From: "Ioannis Aslanidis" <aslanidis@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x86 toolchain changes heads up
Date: Wed, 18 Jul 2007 11:16:13 +0200 [thread overview]
Message-ID: <ea440b1d0707180216x54f668e6ma879594e5cd6b3cf@mail.gmail.com> (raw)
In-Reply-To: <1184748819.9888.8.camel@tuxhugs>
I think it's the other way arround. -march=ix86 is implicit unless you
override it with a user variable.
On 7/18/07, Peter Gordon <codergeek42@gentoo.org> wrote:
> On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote:
> > historically, gcc on x86 has always defaulted to i386. some people noticed
> > recently that glibc-2.6 fails to build in this situation as they were only
> > setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will
> > default -march based on your CHOST. so all the i686-* people will now have a
> > default -march=i686 implied in their gcc systems, i586-* people will
> > have -march=i586, etc... keep in mind this is merely the default.
> > -mike
>
> Does this mean that any user-set "-march" flag is overridden for these
> cases? Just curious.
>
> Thanks.
> --
> Peter Gordon (codergeek42)
> Gentoo Forums Global Moderator
> GnuPG Public Key ID: 0xFFC19479 / Fingerprint:
> DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479
> My Blog: http://thecodergeek.com/blog/
>
>
>
--
Ioannis Aslanidis
<deathwing00[at]gentoo.org> 0xB9B11F4E
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-18 9:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 23:47 [gentoo-dev] x86 toolchain changes heads up Mike Frysinger
2007-07-18 8:53 ` Peter Gordon
2007-07-18 9:16 ` Ioannis Aslanidis [this message]
2007-07-18 9:19 ` Vlastimil Babka
2007-07-18 13:35 ` [gentoo-dev] " Ryan Hill
2007-07-18 14:06 ` [gentoo-dev] " Andrew Gaffney
2007-07-18 17:04 ` Mike Frysinger
2007-07-19 7:15 ` Peter Gordon
2007-07-18 11:04 ` Tobias Klausmann
2007-07-18 19:05 ` Chris Gianelloni
2007-07-18 19:47 ` Mike Frysinger
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=ea440b1d0707180216x54f668e6ma879594e5cd6b3cf@mail.gmail.com \
--to=aslanidis@gmail.com \
--cc=gentoo-dev@lists.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