Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jun 2006 12:03:02 +0200
From:      Csaba Henk <csaba-ml@creo.hu>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: keeping up with "gnu-libtool -> libtool15"
Message-ID:  <20060620100301.GT49983@beastie.creo.hu>
In-Reply-To: <20060620103357.fg7pmhilckc0wgc0@netchild.homeip.net>
References:  <slrne9f52r.esg.csaba@beastie.creo.hu> <20060620091630.4uid5rgn4000cccg@netchild.homeip.net> <20060620080815.GS49983@beastie.creo.hu> <20060620103357.fg7pmhilckc0wgc0@netchild.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 20, 2006 at 10:33:57AM +0200, Alexander Leidinger wrote:
> Create the dirlist file, run aclocal and then autoconf. I expect that  
> it will work then.

I figured out that libtoolize should be called before aclocal (or else
I get "required file `./ltmain.sh' not found".

However, even doing that is not sufficient: while the configure script
will be generated with no apparent failure, it still bails out
out with

  /usr/local/bin/bash: ./ltconfig: No such file or directory
  configure: error: libtool configure failed

The same happens if I call autoreconf.

 * * *

Doing that also reveals what I see as the _real_ problem (which goes
beyond my actual misery with FUSE): the non-gnu-prefixed versions of
autotools are not a _transparent_ drop-in replacement for the
gnu-prefixed ones. That is, autoreconf (which is then autoreconf259)
will fail with 

  Can't exec "aclocal"

So one have to look for workarounds for making autoreconf259 find
aclocal19 as aclocal (and so on). (Or did I miss some knob which will
have this effect globally?)

Regards,
Csaba



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060620100301.GT49983>