From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20191 invoked by alias); 11 Jan 2010 20:42:01 -0000 Received: (qmail 20180 invoked by uid 22791); 11 Jan 2010 20:42:00 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from static-213.50.114.146.addr.tdcsong.se (HELO mail.icomera.com) (213.50.114.146) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 Jan 2010 20:41:50 +0000 Received: from [192.168.0.4] (80.229.223.150) by mail.icomera.com (192.168.64.17) with Microsoft SMTP Server (TLS) id 8.1.240.5; Mon, 11 Jan 2010 21:41:41 +0100 Message-ID: <4B4B8D05.60100@icomera.com> Date: Mon, 11 Jan 2010 20:42:00 -0000 From: Richard Strand User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: "Yann E. MORIN" CC: "crossgcc@sourceware.org" Subject: Re: [PATCH 2 of 2] companion_tools/autoconf: add autoconf tool References: <8dc1ca6bea93dc1d69ab.1263218276@richard-laptop> <201001111947.28377.yann.morin.1998@anciens.enib.fr> <4B4B829F.5090701@icomera.com> In-Reply-To: <4B4B829F.5090701@icomera.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2010-01/txt/msg00082.txt.bz2 Richard Strand wrote: > Yann E. MORIN wrote: > >>> + 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. > 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 Regards, Richard Strand -- For unsubscribe information see http://sourceware.org/lists.html#faq