From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: New computer and Gentoo
Date: Fri, 22 Jul 2011 08:45:56 +0200 [thread overview]
Message-ID: <4E291CA4.8040800@binarywings.net> (raw)
In-Reply-To: <j0a9jp$tp0$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Am 22.07.2011 00:35, schrieb walt:
> On 07/20/2011 10:54 PM, Bill Kenworthy wrote:
>
>> So not sure about march=native now as it is only what was built with
>> native thats been problematic.
>
> Makes me wonder if gcc and glibc need to be recompiled with arch=native
> before rebuilding the rest of the system?
>
>
>
No. See my posts in the other part of this thread where threading was
once broken by a stupid mobile phone MUA.
Every "native" setting is just resolved by gcc at compile time to some
concrete setting like "core2". There is nothing magical about it and you
also don't need to recompile glibc or gcc any more than you need after
switching your march settings between two other settings.
No one had any breakage during the time when -march=core2 was introduced
and all Core2 owners switched from -march=nocona to -march=core2. There
should be no more breakage when switching to "native".
Correlation does not imply causation.
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2011-07-22 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 2:23 [gentoo-user] New computer and Gentoo CJoeB
2011-07-21 2:29 ` Adam Carter
2011-07-21 5:26 ` Mick
2011-07-21 5:54 ` Bill Kenworthy
2011-07-21 22:35 ` [gentoo-user] " walt
2011-07-22 6:45 ` Florian Philipp [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=4E291CA4.8040800@binarywings.net \
--to=lists@binarywings.net \
--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