Alexander Hansen <akh <at> finkproject.org> writes: > > Phaseon wrote: > > Is there a way I can permanently set compilation flags (-arch) to > > ppc64? According to the Apple developer Documentation you are supposed > > to set -arch pp64 in the makefile so that gcc compiles 64bit PowerPC > > binaries but would you not first execute ./configure -arch ppc64 or > > make -arch ppc64?Is there someway to just compile 64 bit binaries by > > default instead of modifying makefiles so that make "Passes on" the > > message to GCC? > > > > Thank you in advance, > > Luis > > > > -- > > "I thought what id' do was id' pretend I was one of those deaf-mutes" > Current versions of fink (0.26 and later) are set up to build 64-bit > libraries for packages that are flagged to require them. Check out the > Packaging manual: > > http://www.finkproject.org/doc/packaging/packaging.en.html > > and do a search for 64. > > The short answer is that you could do it, but it requires modifying > every package description (.info) file for every package that you're > planning to build. >
I would like to reopen this thread because I am having problems with 32-bit vs 64-bit compatibility issues with Leopard on an Intel MacBook. I have an application that I want to build in 64-bit mode, since it compiles against other 64-bit libraries on my system. I am in particular having trouble with fink's openmotif3 (libXm) and gfortran. My best attempts at google searches on 64-bit builds in fink have only revealed the packaging manual link Hansen gives below (which doesn't help me since I'm not making packages, I just want to install them), and discouraging remarks on random pages about fink and 64-bit compatibility in general, e.g. http://search.cpan.org/~rgarcia/perl-5.10.0-RC2/README.macosx#64-bit_PPC_support Anyway, from what I read below, it seems to me that a package should compile as 64-bit on my system if the appropriate flag is set in the package. Or maybe it is that a package will only be compiled as a 64-bit library if another package requires the 64-bit version of that package. Can someone clear up Hansen's explanation on this? But out of ~180 installed packages on my system, I seem to have no directories like /sw/lib/x86_64 or /sw/lib64 or anything denoting "64", whatever it is supposed to be. And given the linking and runtime problems I'm having, it seems to me that I have all 32-bit libaries. So either none of the packages I installed are capable of compiling in 64-bit, or none of them required 64-bit, or I am misunderstanding what it takes for a package to be compiled as 64-bit. So what I want to know is how do I get 64-bit versions of packages in general. Is there a way I can hide packages that do not allow the option to install in 64-bit mode, and force install to choose the 64-bit option? For example, is it possible to add a "use-64bit-exclusively" option to fink.conf? Or is there a way to require packages to compile in 64-bit mode if they have the appropriate flag set? Or if I'm completely misunderstanding how this all works? Thanks, Jason ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
