On Wed, Jan 11, 2006 at 12:02:36PM -0500, Josh Grosse wrote: > On Mon, Jan 09, 2006 at 12:04:27AM +0100, Marc Espie wrote: > > We're now almost done converting all ports to SHARED_LIBS, and a huge > > subset of them to USE_LIBTOOL instead of building their ports. > > I've noticed that USE_LIBTOOL means that devel/libtool must be a dependency. > At least I discovered this when doing a -current rebuild of my relatively > small set of packages, and having gettext fail with an Error Code 127 because > libtool wasn't found in /usr/local/bin. :-)
If USE_LIBTOOL=Yes then libtool is added as a build time dependency and libtool gets installed. This works fine, at least on all of the developer's systems... Maybe you could give us a list of steps to reproduce? > Its not a biggie, but ... I guess my question is: will libtool will be > moved to userland or /usr/ports/mk once things are stabilized? Things are stabilized.
