From: Alexander Holler <holler@ahsoftware.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Optimized Qt
Date: Sat, 08 Jun 2002 12:42:36 +0200 [thread overview]
Message-ID: <146440000.1023532956@krabat.ahsoftware> (raw)
In-Reply-To: <200206081207.22251.danarmak@gentoo.org>
Hello,
--On Samstag, Juni 08, 2002 12:07:17 +0300 Dan Armak <danarmak@gentoo.org>
wrote:
> Please see bug #1571. I haven't had time to "investigate" beyond what the
> comments say. If we could get a good rule of what CFLAGS work and what
> don't I'd be willing to itroduce the thing into the qt ebuilds.
I've just got the same bug with reloads building qt3 with customized
CFLAGS. This gcc bug looks like some bugs I've got trying to build gentoo
with gcc 3.1. With the difference that gcc 3.1 kindly asks for filling out
bug reports. ;)
And I agree that it isn't a good idea to use customized flags if qmake
records these flags for future buildings (specially the processor flags).
Alexander
prev parent reply other threads:[~2002-06-08 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0206071146010.14744-100000@thunderbird.junta.iitk .ac.in>
2002-06-07 6:20 ` [gentoo-dev] Optimized Qt Prashanth Aditya Susarla
2002-06-08 8:23 ` Alexander Holler
2002-06-08 9:07 ` Dan Armak
2002-06-08 10:42 ` Alexander Holler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=146440000.1023532956@krabat.ahsoftware \
--to=holler@ahsoftware.de \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox