On Apr 8, 2011, at 8:00 PM, Ralf Wildenhues wrote:
> Hello Matthijs,
>
> * Matthijs Möhlmann wrote on Fri, Apr 08, 2011 at 04:00:32PM CEST:
>> /bin/sh ../../libtool --mode=compile cc -Wall -g -D_FILE_OFFSET_BITS=64
>> -D_GNU_SOURCE -O2 -I../../include
>> -I/home/matthijs/debpkg/openldap/t/openldap-2.4.25/include
>> -DLBER_LIBRARY -c
>> /home/matthijs/debpkg/openldap/t/openldap-2.4.25/libraries/liblber/assert.c
>> eval: 1: base_compile+= cc: not found
>> eval: 1: base_compile+= -Wall: not found
>
>> This can be reproduced when setting the sh shell to dash, when I set it
>> to /bin/bash everything is fine and the build goes well.
>>
>> I'm not sure if this is an error on my part and that I have to fix it.
>
> This usually happens if configure has chosen bash as $CONFIG_SHELL, but
> somehow /bin/sh is then later put as SHELL in the Makefile.
>
> Does your configure.ac or any included macro files contain explicit
> overrides of $SHELL or $CONFIG_SHELL? Does any of your Makefile.am
> files (or Makefile.in if you don't use automake) explicitly set SHELL
> (rather than using @SHELL@ from configure)?
>
> If /bin/sh is used during configure's tests, then the generated libtool
> script will not use '+='.
>
> Hope that helps.
>
> Cheers,
> Ralf
Hello Ralf,
I see in
build/top.mk:
SHELL = /bin/sh
And the aclocal.m4 contains lines like:
# Check that we are running under the correct shell.
SHELL=${CONFIG_SHELL-/bin/sh}
configure.in does not contain CONFIG_SHELL or SHELL variable.
I've searched through the Makefile.in files, no explicit setting to /bin/bash
or /bin/sh or any other shell. Maybe I'm overlooking something.
Any idea how to debug this? (I now got also bug #621925)
Regards,
Matthijs Möhlmann
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
