On Jul 7, 2008, at 15:32, Martin wrote: > Sorry to have made it more confusing. > > I did not have MacPorts installed until 2 days ago. > > I am using MAMP, simply because it is easy. ImageMagick was a > standalone installation (so, not the MacPorts version). > ImageMagick required the DYLD_LIBRARY_PATH to be extended. > > I also added MAMP's lib dir to the DYLD_LIBRARY_PATH. > > After installing MacPorts I ran into library conflicts with MAMP > and initially prepended /opt/local/lib to DYLD_LIBRARY_PATH > > That seemed to work for installation but not for runtime. > > I am now running without the DYLD_LIBRARY_PATH changed for MAMP and > MacPorts and it all works. > > I guess the moral of the story is to keep the .profile as clean as > possible. > > And I will probably move from MAMP to MacPorts too. > > But it all works at the moment so I am reluctant to switch them. > Then again, the reason to start using MacPorts is the ability to > use variants and to keep up to date with versions.
The moral of the story is not to use DYLD_LIBRARY_PATH. :) Any software that requires you to use that variable is pretty much broken. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
