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 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.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
