Re: Mac OSX

[D . Walsh]

On Mar 07, 2005, at 17:42, Peter O'Gorman wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> D.Walsh wrote:
> | Any luck with generating a patch that allows libtool to work 
> properly in
> | the Macintosh environment or has this ball been dropped already?
> |
>
> GNU Libtool does work properly in the Mac OS X environment. The fact 
> that
> you installed in /usr and overwrote a completely different program 
> (Apple's
> libtool) is something that GNU libtool should deal with one day, but 
> had you
> read your man pages you would not have done that...
>
> If you really must install GNU libtool into /usr (and I advise against 
> it)
> you should do something like:
>
> ./configure --prefix=/usr --program-prefix=g
> make
> sudo make install
>
> This is what Apple does when building GNU libtool, and what most 
> package
> tools do too. Some packagers also add a symlink libtoolize -> 
> glibtoolize,
> you may wish to do so too.
>
> Peter

Peter, are you trying to tell me that the "libtool" supplied and 
installed in Mac OSX is not the "GNU libtool"?

Apple documentation claims that it is.

Based on some software requirements, upgrading of libtool is required, 
currently doing this upgrade breaks libtool, so doing a program prefix 
is not a solution to the issue of upgrading libtool because the test is 
doen against libtool and not glibtool.

A better approach would be to examine what is done in the supplied Mac 
libtool and duplicating the changes in the newer version because doing 
a program prefix doesn't let any software know that libtool has been 
upgraded and this is what is causing all of the problems.

-- Dale