On Jun 23, 2011, at 01:17, Jeremy Huddleston wrote: > On Jun 22, 2011, at 18:52, Ryan Schmidt wrote: > >> On Jun 21, 2011, at 22:17, [email protected] wrote: >> >>> Revision: 79640 >>> http://trac.macports.org/changeset/79640 >>> Author: [email protected] >>> Date: 2011-06-21 20:16:58 -0700 (Tue, 21 Jun 2011) >>> Log Message: >>> ----------- >>> wine-devel: Fixes for darwin11 >>> >>> Also fixed reference to libwine and removed an unrecognized configure option >> >> >>> file rename ${destroot}${prefix}/bin/wine >>> ${destroot}${prefix}/libexec/wine/wine >>> + system "install_name_tool -change >>> @executable_path/../lib/libwine.1.dylib >>> @executable_path/../../lib/libwine.1.dylib >>> ${destroot}${prefix}/libexec/wine/wine" >>> >> >> Huh. I agree that looks like something that was wrong, and should be fixed >> as you did, given how we move the wine executable from bin/ to >> libexec/wine/. But what problem did you encounter that prompted this change? > > I wanted to run wine directly without the DYLD_FALLBACK_LIBRARY_PATH to debug > problems on Lion. The reason it never was an issue was because the > executable is usually started via the wine script (which sets > DYLD_FALLBACK_LIBRARY_PATH and thus allows libwine.dylib to be found via that > route). > >> I wonder why I never had any problem using wine before this. Also, there are >> many other libraries installed by wine that use this @executable_path crap; >> do they need to be changed as well? I'd really like to use absolute paths >> and dispense with the entire @executable_path thing. > > Yeah, I did a followup change in wine-crossover-games to modify those as > well, but I didn't move them into wine and wine-devel. I didn't change them > to absolute paths because I wasn't sure if the port was used relocatably by > anyone ... of course if they were, they'd experience the same problems with > the absolute path as they were with the incorrect relative paths, so perhaps > they should just be changed to absolute paths.
I would love to not have that wrapper script either. If using install_name_tool like this (well, with absolute paths) is all it takes, then I'd love to make that change. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
