Re: Can't build binutils 2.13.90 20021228 on sparc64-linux: configure failure in opcodes

[Christian Jönsson <c dot christian dot joensson at telia dot com>]

On Sun, Dec 29, 2002 at 02:02:25PM -0200, Alexandre Oliva wrote:
> On Dec 29, 2002, Christian Jönsson <c.christian.joensson@telia.com> wrote:
> 
> >> Could you please try to find out what arguments had been passed to
> >> opcodes/configure?
> 
> > hmm, how do I do that?
> 
> Looking for HOST_CONFIGARGS in the top-level Makefile.

well, this is what I have there: 

# This is set by the configure script to the arguments to use when configuring
# directories built for the host system.
HOST_CONFIGARGS = --cache-file=.././config.cache --build=sparc64-linux --host=sparc64-linux --target=sparc64-linux  --with-gnu-as --with-gnu-ld  sparc64-linux --prefix=/usr/local/gcc-binutils --enable-shared --enable-threads=posix

# This is set by the configure script to the arguments to use when configuring
# directories built for the target.
TARGET_CONFIGARGS = --cache-file=../config.cache --host=sparc64-linux --build=sparc64-linux --enable-multilib  sparc64-linux --prefix=/usr/local/gcc-binutils --enable-shared --enable-threads=posix
 
> I suppose the problem is that it's passing all of --build, --host and
> sparc64-linux.  Could you try switching from nonopt to --build or
> --host, and let me know?  I'll have to do some further tweaking to get
> it to work for this case.

sure, tried --host=sparc64-linux instead of sparc64-linux what so
ever, it works. i'll post test results in a short while.

but, it should work the way it used to, right?

Cheers,

/ChJ