From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RJwPo-0005nc-Kl for garchives@archives.gentoo.org; Sat, 29 Oct 2011 00:04:48 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 48CD0E01C9; Sat, 29 Oct 2011 00:04:36 +0000 (UTC) Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 6E575E0138 for ; Sat, 29 Oct 2011 00:03:14 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so1397519bkb.40 for ; Fri, 28 Oct 2011 17:03:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=d6LVXHUuig3wN+mK96P8SzcspiDupKt7/AT8Emna9t0=; b=NN1NUikznAWBherK+OfBMGNgrrUWEcEAFsxq70mNP/GkAbdJyhSKINdP6GmYrdBr1c Lsx1uPKoESCvFw3YOq/95tMiViiUQJiQy7RmlfGqY9hA10KfXima2EH1csietEwHAMBI I7+Zm3utHe3256wxOqH+gMz6ROYZeqvdUDrzo= 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.204.13.132 with SMTP id c4mr4028124bka.23.1319846593521; Fri, 28 Oct 2011 17:03:13 -0700 (PDT) Received: by 10.204.37.16 with HTTP; Fri, 28 Oct 2011 17:03:13 -0700 (PDT) Date: Fri, 28 Oct 2011 20:03:13 -0400 Message-ID: Subject: [gentoo-user] Calls compiler directly, and strange parameters passed. Is this a bug? From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: X-Archives-Hash: 92e9f4487a8933e3dd86a2398e3e0ae1 Just update calibre, and it looks like it builds a bunch of Python extensions. In the build output, I see many things like these: g++ -O3 -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -march=amdfam10 -mcx16 -msahf -mpopcnt --param l1-cache-size=64 --param l1-cache-line-size=64 --param l2-cache-size=512 -mtune=amdfam10 -O2 -pipe -ggdb -pthread -I/usr/include/python2.7 -DPNG_SKIP_SETJMP_CHECK -DPOPPLER_OLD_LINK_TYPE -I/usr/include -I/usr/include/ImageMagick -I/usr/include/poppler -c /var/tmp/portage/app-text/calibre-0.8.23/work/calibre/src/calibre/ebooks/pdf/images.cpp -o /var/tmp/portage/app-text/calibre-0.8.23/work/calibre/build/objects/pdfreflow/images.o gcc -O3 -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -march=amdfam10 -mcx16 -msahf -mpopcnt --param l1-cache-size=64 --param l1-cache-line-size=64 --param l2-cache-size=512 -mtune=amdfam10 -O2 -pipe -ggdb -pthread -I/usr/include/python2.7 -I/usr/include/ImageMagick -c /var/tmp/portage/app-text/calibre-0.8.23/work/calibre/src/calibre/utils/magick/magick.c -o /var/tmp/portage/app-text/calibre-0.8.23/work/calibre/build/objects/magick/magick.o For reference, here are my CFLAGS: CFLAGS="-march=amdfam10 -mcx16 -msahf -mpopcnt --param l1-cache-size=64 --param l1-cache-line-size=64 --param l2-cache-size=512 -mtune=amdfam10 -O2 -pipe -ggdb" CXXFLAGS="${CFLAGS}" It looks like the package adds "-O3 -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC" before appending CFLAGS or CXXFLAGS to the line, and it's calling 'gcc' or 'g++' directly, rather than x86_64-pc-linux-gnu-gcc, x86_64-pc-linux-gnu-g++ or something more generic. It was my understanding that the 'right' way to create a build system is to use the compiler for the target platform. I *think* that means the commands I noted, but I'm uncertain (And there's that it uses -O3, which is a bit spooky, and makes me worry more about the effects of compiler upgrades) Is this incorrect? Does it qualify as a bug? -- :wq