From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: GCC-4.3.2
Date: Mon, 06 Apr 2009 11:56:57 +0300 [thread overview]
Message-ID: <grcg4h$14m$1@ger.gmane.org> (raw)
In-Reply-To: <20090406060221.GH6904@syscon4.inet>
Joseph wrote:
> On 04/03/09 10:34, alain.didierjean@free.fr wrote:
>> Has one of you guys already switched from gcc-4.1.2 to gcc-4.3.2 and
>> performed "emerge system" ?
>> What gives ? Any problem ? Is it worth it right now ? Please tell...
>>
>> --
>> ~adj~
>
> I just notice that there is a problem with CFLAGS -march=native on AMD64
> I recompile my system using this new flag and have a lot of problems. an
> examples new xorg-server-1.5... would not compile, I switch back to my
> previous settings:
> -march=athlon64 and it compiled on first pass.
> So, now I'm recompiling the system with my old flag: -march=athlon64 :-/
-march=native is only useful if you don't know what to use. I guess
most Gentoo users do know what to use. Why should I use "native" if I
know that my CPU is "athlon64" :P
next prev parent reply other threads:[~2009-04-06 8:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 8:34 [gentoo-user] GCC-4.3.2 alain.didierjean
2009-04-03 10:24 ` Thomas Kahle
2009-04-03 12:17 ` Masood Ahmed
2009-04-03 21:15 ` Neil Bothwick
2009-04-03 21:28 ` Jerry McBride
2009-04-04 5:43 ` Mike Kazantsev
2009-04-04 8:28 ` Graham Murray
2009-04-03 14:53 ` alain.didierjean
2009-04-04 7:03 ` Christopher Walters
2009-04-06 6:02 ` Joseph
2009-04-06 8:56 ` Nikos Chantziaras [this message]
2009-04-06 16:35 ` [gentoo-user] GCC-4.3.2 Joseph
2009-04-06 20:07 ` Neil Bothwick
2009-04-06 20:28 ` Joseph
2009-04-06 20:37 ` Paul Hartman
2009-04-06 22:20 ` Neil Bothwick
2009-04-06 16:53 ` Jarry
2009-04-06 17:52 ` Joseph
2009-04-07 2:53 ` Nikos Chantziaras
2009-04-07 1:00 ` [gentoo-user] GCC-4.3.2 Jorge Morais
2009-04-07 2:19 ` Joseph
2009-04-07 14:42 ` Mike Kazantsev
2009-04-07 16:48 ` Arttu V.
2009-04-07 18:07 ` Joseph
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='grcg4h$14m$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@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