On Wed, Sep 21, 2005 at 07:55:33PM +0100, Phil Endecott wrote:
> I have reached the next obstacle in my attempt to cross-compile to
> Debian armeb from my Debian x86 PC: I need a libtool.
> I'm not sure whether I need a way to make the libtool that I already
> have on my build machine know about cross-compiling, or whether I need a
> separate target-specific version. I tried the former approach:
> $ libtool --mode=compile armeb-linux-g++ -Wall -O -o foo.lo -c foo.cc
> libtool: compile: unable to infer tagged configuration
> libtool: compile: specify a tag with `--tag'
> Hmm, --tag is not mentioned in the libtool documentation as far as I can
> On the other hand, I can't see a way to build a libtool for
> cross-compilation; it's configure options include --build and --host,
> but not --target which I think is what I would need [though I am easily
> confused by the difference between cross-compiling libtool and building
> a libtool to use for cross-compiling...].
> Can anyone point me in the right direction? The only mentions of
> cross-compiling and libtool that I can find on the web are in the
> context of automake, which I'm not using in this case.
We've faced this same problem with Scratchbox, and solved it by building
(read: configuring) libtool with/for each toolchain separately.