Alexander K. Hansen <akh <at> finkproject.org> writes: > >> Fink builds 32-bit, unless an individual package asks it not to. > >> There's no global option to force Fink to build 64-bit > >> exclusively. > >> > >> You would need to investigate each package and figure out how it > >> wants to build 64-bit, since each probably takes different > >> options to do so. > >> > > Fink doesn't offer user customizations for builds because it's > completely the opposite of the overarching paradigm under which it > operates: packages should build the same way on different machines as > much as possible. This is the policy for _everything_, not just 32 > vs. 64 bit builds. > > The main reason that we have the 64-bit option in the first place is > that some packages autodetect the machine that they're on and build > accordingly, and we wanted to prevent the case of libraries built on a > G5 being installed and breaking on a G4b, for example.
Thanks for the explanation. I can understand the desire to make fink work the same on all systems. But as the computing world drifts closer and closer to 64-bit everything, it seems to me that eventually fink will be self consistent but incompatible with everything else on the system. Is this the plan for the future? Or is the idea that more and more 64-bit packages will be provided, with names like "[package]-64bit"? In that case, would an appropriate avenue for me be to approach the package distributors (e.g. for openmotif3) and ask for a 64-bit version (like openmotif3-64bit)? ------------------------------------------------------------------------- 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
