2010 09:11, Ralf Wildenhues <[email protected]> wrote: > * Tim Retout wrote on Thu, Oct 14, 2010 at 09:36:07AM CEST: >> I almost just closed #570723 - but I'll reassign to libtool, because >> maybe it should 'set -e' or something (unless that's not portable). > > Issues such as this: > > | eval: 1: libtool_args+=: not found > | eval: 1: libtool_args+=: not found > > typically come from configure running the tests under a different shell > than libtool. This is often because the configure.ac messes with $SHELL > and/or $CONFIG_SHELL, or CONFIG_SHELL is set in the environment. > > The build log referenced looks like it ran under bash: > > | checking whether the shell understands some XSI constructs... yes > | checking whether the shell understands "+="... yes > > yet make uses /usr/lib/rep/x86_64-pc-kfreebsd-gnu/libtool which doesn't > seem to have been created by configure. I suspect that > /usr/lib/rep/x86_64-pc-kfreebsd-gnu/libtool assumes /bin/sh is bash, > because at the time and on the system it was created it was bash. > > In all likelihood, this is not a Libtool bug.
Yep, this specific problem is with librep-dev not setting CONFIG_SHELL explicitly, and I'll fix that in #570719. But the bug I wanted to raise was that this general class of errors - running the libtool script with the wrong shell - does not cause a bad error code. If 'set -e' were added at the top of libtool, it would fail early. Feel free to 'wontfix' if that's not possible to do. -- Tim Retout <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
