David van der Spoel wrote: [] >> > Can't one just set some compiler flags -m64 for C, C++ and linking? Why
I didn't say it was difficult, did I? Making Fink packages is often not difficult. In particular if you start from an existing package, then all the "bureaucratic" parts of the package description, like license, source URL, description, home page etc, are already present, you "only" have to deal with the addition of compiler flags. And maybe paying attention where to install teh resulting files, so that 32bit and 64bit variants don't conflict. > does one need to meddle with all the packages? Assuming most packages > are configured with autoconf, adding --host=x86_64-apple-darwin > --build=x86_64-apple-darwin to the configure line should probably suffice. Perhaps. The hard work in creating a Fink package is often just this "probably", "most packages...". You have to find out what really works. You have to find out how to get the compiler flags into the build system. And this work is the same if you do it by hand for just one compilation or for a Fink package so that others can benefit, too. If I look at the two Fink packages that have 64bit variants, I see that in gmp, the configure switch for 64bit is - ABI=64 if it is compiled on intel and - ABI=mode64 if it is compile on ppc, whereas in libmpfr1 one has to - export CC="gcc -m64" before running configure. This is all very simple, but not one-size-fits-all. -- Martin ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel
