From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id EF3A01381F3 for ; Sat, 17 Aug 2013 16:10:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DFCCAE0AFF; Sat, 17 Aug 2013 16:10:20 +0000 (UTC) Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E8766E0A8E for ; Sat, 17 Aug 2013 16:10:19 +0000 (UTC) Received: by mail-oa0-f47.google.com with SMTP id g12so3445691oah.6 for ; Sat, 17 Aug 2013 09:10:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=nHOhn2boAz09d8JgHDvc60Q+VKX8WsALljiUUFk8G+E=; b=cu97t2mlsCafd77vboNh2VtSHFI36ac2knMdeR1IhLRWbeatGw8G/2G5kS+t51l9eJ HkdRfgeGyEjy4yAjrXvxfTV6X10E5ka2VcuAv+9HKhMHxDmvizQmDBrZ4W44Ibz/sEKG BjSuxm/ULrbdlGX7KMR9Obw05vUN8mUX2oLFMTjTZB3Vozi84tByHnBXgx7KzovDZmrq lzF5YGsiPXogIpDLzKmiuJgnLiJI7Z+ev2+cZiMUQ8v1MvNKjnFzt/c5PLz6ffDfsMnE vPZL3ayyUtxK1bMwpD6QHESVcXs8vR7QwDxUIuQsuI9M4EwzIE5SsvimuXT9e2eNdfzv VngQ== X-Received: by 10.60.80.167 with SMTP id s7mr3591384oex.38.1376755819091; Sat, 17 Aug 2013 09:10:19 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.60.52.79 with HTTP; Sat, 17 Aug 2013 09:09:39 -0700 (PDT) In-Reply-To: <20130816223802.GB30183@waltdnes.org> References: <20130816223802.GB30183@waltdnes.org> From: Francisco Ares Date: Sat, 17 Aug 2013 13:09:39 -0300 Message-ID: Subject: Re: [gentoo-user] Re: emerge -e errors right after install To: gentoo-user Content-Type: multipart/alternative; boundary=089e01228b148a29e904e426f1a3 X-Archives-Salt: d7ea2d34-491a-4814-8428-28622c23d158 X-Archives-Hash: 74d826b4daa1d0122f4e4b1fff891d7d --089e01228b148a29e904e426f1a3 Content-Type: text/plain; charset=UTF-8 2013/8/16 Walter Dnes > On Fri, Aug 16, 2013 at 03:18:35PM -0300, Francisco Ares wrote > > > You were right. I have overlooked the type of the new machine's CPU (it > is > > a "Pentium(R) Dual-Core CPU" and the other one, already working, is a > > "Intel(R) Core(TM)2 Duo CPU"). So, a "march=nocona" instead of a > > "march=core2" seems to have solved the problem. > > 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. > > -- > Walter Dnes > I don't run "desktop environments"; I run useful applications > > Yes, that is the problem. I got the oldest CPU on witch the same binaries will run. The newest uses an Intel I3, but the oldest ones run on a "Dual Core" (not "Core-2", as my first assumption). Thanks for the other parameters though, I have never tried them. Gonna take a look. Francisco --089e01228b148a29e904e426f1a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= 2013/8/16 Walter Dnes <waltdnes@waltdnes.org>
On Fri, Aug 16, 2013 at 03:18:35PM -0300, Francisco Ares wrote

> You were right. =C2=A0I have overlooked the type of the new machine= 9;s CPU (it is
> a "Pentium(R) Dual-Core =C2=A0CPU" and the other one, alread= y working, is a
> "Intel(R) Core(TM)2 Duo CPU"). So, a "march=3Dnocona&qu= ot; instead of a
> "march=3Dcore2" seems to have solved the problem.

=C2=A0 I have the following in make.conf

CFLAGS=3D"-O2 -march=3Dnative -fomit-frame-pointer -pipe -fno-unwind-t= ables -fno-asynchronous-unwind-tables"
CXXFLAGS=3D"${CFLAGS}"

...where "-march=3Dnative" will always work correctly for a local= build.
The only possible worry is if you're cross-compiling and or distributin= g
a binary to multiple machines. =C2=A0It also saves me the headache of
figuring out the CFLAGS setting whenever I get a new machine. =C2=A0You sti= ll
have to set up the correct processor in the kernel, however.

--
Walter Dnes <waltdnes@waltdnes.= org>
I don't run "desktop environments"; I run useful applications=


Yes, = that is the problem. I got the oldest CPU on witch the same binaries will r= un. The newest uses an Intel I3, but the oldest ones run on a "Dual Co= re" (not "Core-2", as my first assumption).

Thanks for the other parameters though= , I have never tried them. Gonna take a look.

Francisco
--089e01228b148a29e904e426f1a3--