problems with ld/configure

problems with ld/configure

[Andrija Radicevic]

Hi,

when building binutils-2.16  (for a new target) it fails on building ld, 
saying that the target is not listed in config.sub file. Which is not the 
case.
Examining the ld/configure script I have found that the section :

    # Canonicalize the secondary target names.
    result=`${CONFIG_SHELL-/bin/sh} $ac_config_sub $targ_alias 2>/dev/null`
    if test -n "$result"; then
        targ=$result
    else
        targ=$targ_alias
    fi

    . ${srcdir}/configure.tgt

fails to produce the correct target alias.

It turnd out that
${CONFIG_SHELL-/bin/sh} evaluates to /bin/sh
and
$ac_config_sub to /bin/sh ../../binutils-2.16/ld/../config.sub
which together obiously results with an awkward construct

I have a duplicated /bin/sh part, so the produced commandline would be:

/bin/sh /bin/sh ../../binutils-2.16/ld/../config.sub

I have found that the configure.in file contains exactly the same part of 
the code, so I guess that the configure was generated correctly. So, either 
${CONFIG_SHELL-/bin/sh} should evaluate to empty string or $ac_config_sub 
should evaluate to ../../binutils-2.16/ld/../config.sub

What went wrong? Could someone help me please.

best regards


Andrija Radicevic 

Re: problems with ld/configure

[Andreas Schwab]

"Andrija Radicevic" <andrija.radicevic@zg.t-com.hr> writes:

> I have found that the configure.in file contains exactly the same part of
> the code, so I guess that the configure was generated correctly. So,
> either ${CONFIG_SHELL-/bin/sh} should evaluate to empty string or
> $ac_config_sub should evaluate to ../../binutils-2.16/ld/../config.sub
>
> What went wrong? Could someone help me please.

The 2.16 release predates the use of autconf 2.50+ for its configure
scripts.  Apparently you have regenerated the configure script with the
wrong version of autoconf: you need to use autoconf 2.13 for that.
Between autoconf 2.13 and 2.50 the value of ac_config_sub has been changed
to include $SHELL.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."