On Sat, Feb 11, 2006 at 10:54:45PM -0600, Robert T Wyatt wrote: > This seems to have worked alright, but I thought it was odd to see a > deployment target of 10.3 on my 10.4.4 machine. Could it be intentional? > > Running Mkbootstrap for Crypt::SSLeay () > chmod 644 SSLeay.bs > rm -f blib/arch/auto/Crypt/SSLeay/SSLeay.bundle > LD_RUN_PATH="/sw/lib" env MACOSX_DEPLOYMENT_TARGET=10.3 cc -bundle > -undefined dynamic_lookup -L/usr/local/lib SSLeay.o -o > blib/arch/auto/Crypt/SSLeay/SSLeay.bundle -L/sw/lib -lssl -lcrypto
Some packages really need that setting on 10.4. Some other packages inherit certain build settings from their dependencies. In the case of -pmXXX packages, the standard perl-module build scripts ask perlXXX what settings were used when building that perlXXX, and then use the same ones. This reduces the chance that a perl module will be built in a manner that made it incompatible with the perl that would try to load it. According to 'perl -V', perl5.8.6 from Apple in Tiger was compiled with: ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc' dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
