[Boost-build] Apple's libtool

From: Michael Witten (mfwitten_at_[hidden])
Date: 2008-06-19 04:43:41

Hello.

It might be a good idea to qualify completely the path to libtool when
building on Mac OS X:

        /usr/bin/libtool

Apple provides its own libtool, which causes endless troubles, because
so many projects simply invoke 'libtool', expecting to get either  
Apple's
or GNU's version.

In my case, I installed GNU's libtool into /usr/local, and this worked
quite nicely with a bunch of GNOME projects.

However, because I setup /usr/local/bin to take highest precedence,  
boost's
build process found GNU's libtool when it wanted Apple's.

While it's probably better that I play by the name game that Apple  
created,
I imagine that it would be fruitful if boost's build process simply  
specified
/usr/bin/libtool explicitly.

This should make the build succeed in virtually all cases on Mac OS X.

Here is a patch that make this change (just `patch -p0 FILE` from  
$src_dir):

--- tools/build/v2/tools/darwinOld.jam	2008-06-19 04:28:19.000000000  
-0400
+++ tools/build/v2/tools/darwin.jam	2008-06-19 04:28:22.000000000 -0400
@@ -213,5 +213,5 @@
  # TODO: Find a way to use the underlying tools, i.e. lipo, to do this.
  actions piecemeal archive
  {
-    libtool -static -o "$(<:T)"  $(ARFLAGS)  "$(>:T)"
+    /usr/bin/libtool -static -o "$(<:T)"  $(ARFLAGS)  "$(>:T)"
  }

Sincerely,
Michael Witten

P.S.
If you wish, cc me in replies.