monotone @0.99.1 will not build due to lua dylib relative link path

[elb@…]

The monotone build process is unable to create mtn.1 because the execution of 'mtn manpage' fails due to a linking problem. Monotone is linked to liblua5.1.dylib via a relative path, which is not correct or available until the monotone binary is installed.

The system is Snow Leopard (10.6.6), ports 1.9.2 updated 2011-03-19.

Copying the monotone binary to /opt/local/bin and generating mtn.1 manually allows the build to proceed and install.

otool -L mtn:

/opt/local/bin/mtn:
	/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.1.0)
	/opt/local/lib/libpcre.0.dylib (compatibility version 1.0.0, current version 1.1.0)
	/opt/local/lib/libbotan-1.8.2.dylib (compatibility version 0.0.0, current version 0.0.0)
	@executable_path/../lib/liblua.5.1.dylib (compatibility version 5.1.0, current version 5.1.4)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.1)
	/opt/local/lib/libsqlite3.0.dylib (compatibility version 9.0.0, current version 9.6.0)
	/opt/local/lib/libidn.11.dylib (compatibility version 18.0.0, current version 18.3.0)
	/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)

The installed monotone dependencies are:

zlib @1.2.5
libiconv @1.13.1
libidn @1.20
gettext @0.18.1.1
boost @1.45.0
lua @5.1.4
pcre @8.12
sqlite3 @3.7.5
botan @1.8.10

Because they may be relevant here, libtool is @2.4, pkgconfig is @0.25.

[tommyd@…]

Interestingly the port installs successfully under 10.5.8 and - now comes the weird thing - liblua is not listed at all in my otool's output. libtool is @2.4 and pkgconfig @0.25 for me as well.

[tommyd@…]

A quick search brought up #28726 which seems to be fixed. The origin of this problem seems to be a change request from #27378 - before that lua build an *.ar file and therefor was apparently statically linked. I'll reinstall lua locally and try to reproduce the problem.

[tommyd@…]

The problem was indeed #28726 - the patch for the aforementioned ticket sets a fixed install path and with this the installation of mtn succeeds.

[anddam (Andrea D'Amore)]

Cc Me!

[anddam (Andrea D'Amore)]

#28726 closed