* Colin Watson wrote on Wed, Jan 16, 2008 at 07:44:30PM CET:
> On Wed, Jan 16, 2008 at 07:18:08PM +0100, Ralf Wildenhues wrote:
> >
> > Actually, the generated libtool script should just have
> > #! /bin/bash
> >
> > as its first line, and not re-exececute itself at all.
> >
> > OK, let's go step by step here: at the end of the trace posted in this
> > bug report, CONFIG_SHELL is exported and contains /bin/bash, and
> > likewise for SHELL. That means config.status should contain as its
> > first line
> > #! /bin/bash
> >
> > and a dozen lines further down
> > SHELL=${CONFIG_SHELL-/bin/bash}
>
> In my failing test case, I have /bin/sh in both these places, not
> /bin/bash.
Hmm. Can you rerun the test, with the 'set +x' removed that I asked you
to add? Probably a good idea to gzip the output to not exceed
bug-libtool list size limits.
> > And in fact that is just what I get on my Debian etch when I try to
> > reproduce your setup as closely as possibl (tested with Libtool CVS
> > HEAD).
>
> What does your /bin/sh symlink point to?
Normally to bash. For doing the test, however, I did this:
Let /bin/sh point to dash. Start zsh, export SHELL=/bin/zsh, unset
CONFIG_SHELL, run ../libtool/configure.
My trace output looks very much like yours, AFAICS.
Cheers,
Ralf
_______________________________________________
Bug-libtool mailing list
Bug-libtool@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool
