public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Prashanth Aditya Susarla <aditya@iitk.ac.in>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Re: GCC3.1 bootstrap fails
Date: Mon, 3 Jun 2002 22:27:05 +0530 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0206032223240.6705-100000@thunderbird.junta.iitk.ac.in> (raw)
In-Reply-To: <4957DDB96FE2D411A5C10008C7A4A126035FE241@dfsmttayz083.hq.af.mil>

> -fomit-frame-pointer -O3 (I had to ebuild parts of Xfree manually so I could
> change the flags in certain areas to get it to compile, and I also had to

Somehow I couldn't manage to do this. There was this problem with one 
particular component (don't remember which, it was posted in one thread on 
this mailing list earlier this month) and there was a quickfix solution 
to it which said that it could be built manually in $PORTAGE_TMPDIR. I 
tried it with all combinations of flags but I couldn't get it to work. 
Ultimately I had to rebuild entire xfree with -march=i686 -O3 
-fomit-frame-pointer -pipe.

I had almost forgotten that qt doesn't honor make.conf and I went ahead 
and built it and to my consternation saw it was using measly -O2 (and no 
architecture-specific) flags. I think I'll just rebuild qt after I am done 
with kde entirely.

Will it be necessary for me to recompile KDE if I recompile qt with these 
newer flags? I shouldn't think so because I don't see any 
qt-statically-linked components in KDE.

Regards,
Prashanth Aditya Susarla




  reply	other threads:[~2002-06-04 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 17:13 [gentoo-dev] Re: GCC3.1 bootstrap fails Zaborowski, Ed, Ctr, AFPCA/OAC
2002-06-03 16:57 ` Prashanth Aditya Susarla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 19:07 Zaborowski, Ed, Ctr, AFPCA/OAC
2002-06-03 18:42 ` Prashanth Aditya Susarla
     [not found] <20020602170104.750B0AC465@chiba.3jane.net>
2002-06-02 17:42 ` Prashanth Aditya Susarla
2002-06-02 21:32   ` Bart Verwilst
2002-06-03  0:53     ` Prashanth Aditya Susarla
2002-06-03  1:18     ` Prashanth Aditya Susarla
2002-06-03  2:07       ` Prashanth Aditya Susarla
2002-06-03  3:52     ` Brian Webb
2002-06-03  6:04       ` Brian Webb
2002-06-03  5:59         ` Prashanth Aditya Susarla
2002-06-04 17:12           ` Matthew Kennedy
2002-06-03 16:49             ` Prashanth Aditya Susarla
2002-06-05  5:51               ` Christian Hergl
2002-06-04  6:05                 ` Prashanth Aditya Susarla

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=Pine.LNX.4.44.0206032223240.6705-100000@thunderbird.junta.iitk.ac.in \
    --to=aditya@iitk.ac.in \
    --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