-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/22/11 5:18 PM, Rogers, Matt wrote: > > On Jun 22, 2011, at 2:53 PM, Alexander Hansen wrote: >> >> You're likely to have problems with Fink if you use third-party >> compilers, libraries, etc. There's no way to guarantee that they're >> compatible. > > I'm already having problems with Fink because of a third-party app > (Java),
That's not our fault. The issue is due to something _Apple_ did on new machines. and if you're suggesting that installing gfortran and associated > libraries (to say nothing of industry standard 'third party' compilers > like ifort) will break fink, then it sounds like fink will be the > software package to go, not the third-party software. > The presence of ifort is _guaranteed_ to break building shared C libraries for Fink's netcdf, due to how the _upstream_ netCDF developers have things set up. I haven't explicitly shut off detection of Fortran compilers in the netcdf _C_ library build as of yet, but that may have to happen. This may no longer be true in the most current upstream netCDF, but I haven't investigated that. > Most end users care more about doing their work with the tools they need > to use than making sure their setup is fink-compatible. Obviously > nobody expects the Fink team to support everybody's and anybody's wacky > custom setups and libraries, but if simple, standard tools like zlib, > libjpeg, and gfortran are enough to break fink, then honestly, I'm > better off not using it. > Define "standard". Typically packages can be built with a number of different options. We use the _system's_ zlib, as provided by the OS. And we provide libjpeg and gfortran. We know that our builds are consistent with our other packages. If your third-party libs are of a different architecture than is your Fink tree, then your builds will fail. If your third-party libs aren't built quite the same as ours, or aren't identical versions, they may be incompatible with our packages, and our builds will fail. It's essentially impossible to keep Apple's build tools from looking in /usr/local. > Point's moot anyways - the Java fix worked (might want to put this in > the Fink documentation - maybe the FAQ page in the specific-package > section?) and thank you all for your quick work! > > cheers, > -- > Matt Rogers, Ph.D. ([email protected] > <mailto:[email protected]>) > Cooperative Institute for Research in the Atmosphere > Colorado State University > > > - -- Alexander Hansen, Ph.D. Fink User Liaison http://finkakh.wordpress.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4CdpcACgkQB8UpO3rKjQ/aQwCfcxGqIODRw6SkZPipb/BvsRiI X6MAnj2ewZFlu2tjjvVQITdKHLIVv+ar =7n/1 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ 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
