|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Sat, 2006-05-06 at 22:12 -0400, Christopher Sean Morrison wrote: > > The configuration problem I mentioned is that the provided installation of > the GNU Autotools on Mac OS X seems to be broken by default for projects > that utilize the autoconf+automake+libtool trio. In particular, running > autoreconf will fail for a project that utilizes libtool during a phase in > autoreconf where 'libtoolize' is invoked. For whatever reason, this is > provided as 'glibtoolize' on Mac OS X causing autoreconf to bail with an > error. The developer must account for the misconfiguration through one of > several possible work-arounds (e.g. set env var, add symlink, run > autoreconf steps one at a time manually, etc). > The reason that it is provided as glibtoolize on darwin is that there is a /usr/bin/libtool provided with the Apple developer tools that is orthogonal to gnu libtool. Thus, GNU libtool is configured with --program-prefix=g, which not only affects libtool, but also libtoolize. Now, many maintainers check for darwin and set LIBTOOLIZE=glibtoolize, but it may be worth a bug report for Apple to include a symlink libtoolize -> glibtoolize in /usr/bin. I don't think it should just be renamed back to libtoolize, both would be best. In my opinion, automake, autoconf and GNU libtool should be in the developer tools packages, also. I have filed bugs previously on the dated automake and GNU libtool, which have been closed as duplicates, so the right people are aware of the issue... Peter
Description: This is a digitally signed message part
_______________________________________________ Do not post admin requests to the list. They will be ignored. Unix-porting mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
|>Re: autotools (From: Christopher Sean Morrison <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.