Re: Problems with libtool 2.2.2 and /bin/sh pointing to dash

[Ralf Wildenhues]

* Ross Burton wrote on Tue, Apr 22, 2008 at 11:11:25AM CEST:
> I can replicate this on my Debian Sid (up to date as of this morning) laptop,
> with the following configuration.
> 
> /bin/sh -> /bin/dash
> SHELL=/bin/bash
> PATH=/home/ross/BUILD/bin:/home/ross/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
> Using libtool 2.2.2-1 from Debian Experimental

I'm having a deja vu feeling, there was a similar Debian bug a while
ago which IIRC I could not reproduce either.

FWIW, I can *not* replicate this with building the Libtool package;
I have set /bin/sh -> dash, SHELL=/bin/bash, and some Debian
stable/testing mix.  Which autoconf version do you use, and which dash
and bash versions do you have installed?  Can you put 
  set -x

as second line in the configure script, and run ./configure and post the
output (either abridged, or bzip2'ed)?  The shell selections parts are
interesting (there may be several of them).

> /usr/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: ignoring invalid character `\001' 
> in
> script
> /usr/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: syntax error in VERSION script
> 
> ./libtool starts with #!/bin/bash, and echoing CONFIG_SHELL at the end of
> configure reveals that it is set to /bin/bash aswell.
> 
> Interestingly if I then re-run configure the build works fine...

Rerun as
  ./configure

or as
  ./config.status --recheck

?  Because the latter will ensure configure is launched using
$CONFIG_SHELL, and with CONFIG_SHELL in the environment.

Thanks,
Ralf