On 4/16/2012 6:11 PM, Mirko Raca wrote: > Hi everybody, > > my problem Fink seems to compile everything for the i386, while it should > be x86_64.
Why "should" ? From your 'fink -V' output, your Fink install is clearly set up for i386. Therefore, everything Fink compiles (with very few well marked exceptions) will be for i386, not for x86_64. > SETUP > > it seems a very common setup, I have a OS X 10.6.8 > > fink -V gives me: > Package manager version: 0.32.6 > Distribution version: selfupdate-rsync Mon Apr 16 17:45:13 2012, 10.6, i386 > Trees: local/main stable/main stable/crypto unstable/main unstable/crypto > > The path is set to > echo $PATH > /sw/var/lib/fink/path-prefix-10.6:/opt/local/bin:/opt/local/sbin:/sw/bin:/sw/sbin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/local/go/bin:/usr/X11/bin: > > (not the cleanest thing in the world, I know) Fink ignores any $PATH that you have set, but its builds do have a high probability of picking up stuff in /opt/local and /usr/local and that is likely to cause other problems down the road. > and I even went to the > /sw/var/lib/fink/path-prefix-10.6/compiler_wrapper > > and forced the architecture on line 17 > exec $compiler -arch x86_64 "$@" > > ------------------ > For e.g. when I try to compile python2.7 I'm getting compile lines (note > the -arch parameter): > > cc -I. -I.. -I../include -fPIC -fno-common -DOPENSSL_PIC -DZLIB_SHARED > -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch i386 > -O3 -fomit-frame-pointer -DL_ENDIAN -DOPENSSL_BN_ASM_PART_WORDS > -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM > -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM > -DWHIRLPOOL_ASM -DGHASH_ASM -I/sw/include -c -o cryptlib.o cryptlib.c Not everything gets sent through the path-prefix wrapper. Some things use other methods to determine the architecture to use, starting with the existence of your Python.framework install. > Is there any way around this? I'm running out of ideas Yes, if you want Fink to compile for x86_64, install Fink as x86_64 when asked about it during the bootsrap install. It is not possible to transition a Fink install from one architecture to another, so you'll have to bootstrap from scratch. <http://finkers.wordpress.com/2009/08/31/starting-anew/> will give you instructions on how to collect your current installed package list, and rebuilding them after installing your new Fink install. You _can_ have an i386 and x86_64 install coexist on the same machine if you give them a different install path during bootstrapping. A common example is to have /sw and /sw64, respectively. For the most part they'll happily coexist and can be erased independently. > ------------------ > SECOND PROBLEM > > During fink update-all, I've recently also started seing > > checking for ld used by gcc... no > configure: error: no acceptable ld found in $PATH > ### execution of ./configure failed, exit code 1 > > LD is present in the $PATH at location /usr/bin/ld > and the version is > @(#)PROGRAM:ld PROJECT:ld64-97.14 > llvm version 2.7svn, Apple Build #2326-10 Without seeing the output from config.log, I would venture that this is due to your having modified path-prefix-10.6 earlier. Hanspeter ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Fink-beginners mailing list [email protected] List archive: http://news.gmane.org/gmane.os.apple.fink.beginners Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners
