This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Yann E. MORIN wrote:I'm not sure if this is relevant but the autoconf documentation seems to suggest running /bin/bash ./configure to insure the same shell is used everywhere: http://www.gnu.org/software/autoconf/manual/autoconf.html#CONFIG_005fSHELL
+ mkdir -p "${CT_BUILD_DIR}/build-autoconf" + CT_Pushd "${CT_BUILD_DIR}/build-autoconf" + CT_DoExecLog ALL ${CONFIG_SHELL} \
Directly call ./configure, do not use CT_CONFIG_SHELL. It's the responsibility of ./configure to use CONFIG_SHELL (note there's no leading CT_) internally. CONFIG_SHELL is correctly set and exported.
I know this is how it is supposed to work, but CONFIG_SHELL actually seems to cause problems on my system. I am using Ubuntu 9.04 where /bin/sh points to dash and SHELL=/bin/bash. When CONFIG_SHELL=/bin/bash then autoconf configure fails on my system with the error "configure: error: no acceptable m4 could be found in $PATH.". When CONFIG_SHELL is not set, or configure is explicitly called with bash then this problem goes away!
I don't experience this issue when building any of the other packages in crosstool-ng. :(
I have attached a text file with output from my shell with an example of
what happens.
-- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |