Problems with using libtool dependencies in opcodes

[Daniel Jacobowitz]

On Wed, Mar 10, 2004 at 03:29:29AM -0300, Alexandre Oliva wrote:
> On Mar  9, 2004, Daniel Jacobowitz <drow@mvista.com> wrote:
> 
> > On Tue, Mar 09, 2004 at 07:29:57PM -0300, Alexandre Oliva wrote:
> >> On Mar  9, 2004, Daniel Jacobowitz <drow@mvista.com> wrote:
> >> 
> >> > It's the host != build that is causing the problem, since libtool
> >> > insists on putting host directories in link commands on the build
> >> > machine.
> >> 
> >> Err...  No it doesn't.  There wasn't any single host directory in link
> >> commands, only /usr/local/lib, that was presumably taken from the
> >> command line flags stored in libbfd.la.
> 
> > /usr/local/lib is a host directory.
> 
> As soon as you configured your toolchain to install in /usr/local/lib,
> you're saying /usr/local is a directory that contains and/or will
> contain libraries for the host.

That's the most useless behavior I've ever encountered.  The logical
corollary is that it is not possible to configure --prefix=/usr on a
build machine without implying that /usr/lib contains libraries for the
host, in other words, that it is not possible to cross-build native
system tools using libtool, with $build != $host, _by design_?

Let's try this from the other end then.  I want binutils installed on
my target in /usr.  I want to build it on a $build != $host system.
How would you recommend configuring it?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer