From: Francisco Ares <frares@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: emerge -e errors right after install
Date: Sat, 17 Aug 2013 13:15:12 -0300 [thread overview]
Message-ID: <CAHH9eM7ep-cz==8v3FFcmEpWJApu9s6POzp726sPSR_8j1M1ng@mail.gmail.com> (raw)
In-Reply-To: <kunv5n$rvj$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
2013/8/17 Michael Palimaka <kensington@gentoo.org>
> On 17/08/2013 08:38, Walter Dnes wrote:
>
>>
>> I have the following in make.conf
>>
>> CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables
>> -fno-asynchronous-unwind-**tables"
>> CXXFLAGS="${CFLAGS}"
>>
>> ...where "-march=native" will always work correctly for a local build.
>> The only possible worry is if you're cross-compiling and or distributing
>> a binary to multiple machines. It also saves me the headache of
>> figuring out the CFLAGS setting whenever I get a new machine. You still
>> have to set up the correct processor in the kernel, however.
>>
>>
> While -march=native is generally good advice, GCC is not perfect and on
> occasion it can flags to be enabled that are not supported, resulting in
> the invalid instruction error.
>
>
>
Thanks, that is a good point to be aware of.
Francisco
[-- Attachment #2: Type: text/html, Size: 1481 bytes --]
next prev parent reply other threads:[~2013-08-17 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 13:22 [gentoo-user] emerge -e errors right after install Francisco Ares
2013-08-16 13:59 ` [gentoo-user] " Michael Palimaka
2013-08-16 14:58 ` Francisco Ares
2013-08-16 18:18 ` Francisco Ares
2013-08-16 22:38 ` Walter Dnes
2013-08-17 13:51 ` Michael Palimaka
2013-08-17 16:15 ` Francisco Ares [this message]
2013-08-17 16:09 ` Francisco Ares
2013-08-17 7:52 ` [gentoo-user] " Stroller
2013-08-17 16:13 ` Francisco Ares
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='CAHH9eM7ep-cz==8v3FFcmEpWJApu9s6POzp726sPSR_8j1M1ng@mail.gmail.com' \
--to=frares@gmail.com \
--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