public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-dev List <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] GCC 3.1/binutils 2.12 and glibc compile problems
Date: 28 May 2002 06:37:29 +0800	[thread overview]
Message-ID: <1022539050.18549.9.camel@rattus> (raw)
In-Reply-To: <20020527211821.23e87de1.webmaster@refstart.nl>

I see an occaisional message with "odd" make flags like this one with
3dnow.  Is there a comprehensive list hidden somewhere?  I am
particularly interested in athlon ones, for gcc-2.95, at least until
gcc3 builds become feasable.

BillK

On Tue, 2002-05-28 at 03:18, Webmaster Refstart.NL wrote:
> Hi all,
> 
> I try to set up a GCC 3.1 based Gentoo system with binutils 2.12. When I try to run ./scripts/bootstrap in the directory /usr/portage, I get errors when compiling glibc (sorry, I can't c/p the output). I've the following compile flags in /etc/make.conf:
> 
> CHOST = i686-pc-linux-gnu 
> CXXFLAGS = -march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O3 -pipe 
> CFLAGS = -march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O3 -pipe
> 
> Is this a bug in glibc or should I use binutils 2.11 (without the combreloc tweak)?
> 
> Thanks in advance,
> 
> Niek.
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev



  parent reply	other threads:[~2002-05-27 22:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 19:18 [gentoo-dev] GCC 3.1/binutils 2.12 and glibc compile problems Webmaster Refstart.NL
2002-05-27 21:50 ` Lars Pechan
2002-05-28  8:46   ` Webmaster Refstart.NL
2002-05-28  8:59     ` Spider
2002-05-28 16:23       ` Webmaster Refstart.NL
2002-06-06  3:07     ` Matthew Kennedy
2002-05-27 22:37 ` Bill Kenworthy [this message]
2002-05-27 22:45   ` Lars Pechan

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=1022539050.18549.9.camel@rattus \
    --to=billk@iinet.net.au \
    --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