Summary: | gnupg-1.4.2 couldn't compile | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Martin Novak <mn> |
Component: | Mac OSX | Assignee: | Gentoo for Mac OS X <ppc-macos> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | OS X | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Novak
2005-08-11 17:26:35 UTC
Which version of gettext do you have installed, and with which use flags? emerge -pv gettext Doesn't look like it has anything todo with gettext. try ditching the -fPIC flag. (In reply to comment #2) > Doesn't look like it has anything todo with gettext. try ditching the -fPIC flag. Hello, I tried to ditch -fPIC flag, and it hasn't helped [ebuild U ] sys-devel/gettext-0.14.4 [0.14.1-r1] (-doc) -emacs +nls 6,869 k did you re-emerge gettext without the -fPIC flag then try again? Alternatively, if you are going to try using the -fPIC flag on Darwin/OS X, you always need to add -fno-common as well, this prevents it from using the same symbol from multiple libs like its doing below. Hi I tried both - without -fPIC - I wasn't event able to compile gettext with -fno-common I was able to compile gettext, but again not gnupg. BTW. I have read some stuff in man gcc, and there is statement: "-fPIC is the default on Darwin and Mac OS X."... Have you tried scaling back your CFLAGS to something relatively harmless such as "-O2 -pipe"? It compiles fine on my machine with the CFLAGS I am using: CFLAGS="-O3 -fgcse-sm -funroll-loops -fstrict-aliasing -fsched-interblock -falign-loops=16 -falign- jumps=16 -falign-functions=16 -falign-jumps-max-skip=15 -falign-loops-max-skip=15 -ffast-math - freorder-blocks -freorder-blocks-and-partition -finline-floor -mpowerpc-gpopt -force_cpusubtype_ALL -mcpu=7450 -fPIC -pipe -maltivec" It looks long, but all those additional options are part of -fast -- I just needed to get rid of a few of them. I just emerged 1.4.2-r1 without any problem ?!? My only suggestion is to try to upgrade world before upgrading gnupg and then retry. We unfortunately cannot reproduce this bug. After you've done that, sudo rm -rf /var/tmp/portage/gnupg-{version}. Then re-emerge gnupg with -fno-common as kito suggested. |