public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: Richard Strand <richard.strand@icomera.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: [PATCH 2 of 2] companion_tools/autoconf: add autoconf tool
Date: Mon, 11 Jan 2010 20:44:00 -0000	[thread overview]
Message-ID: <201001112144.09044.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4B4B829F.5090701@icomera.com>

Richard, All,

On Monday 11 January 2010 20:57:19 Richard Strand wrote:
> Yann E. MORIN wrote:
> > 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!

OK. After all, we're not going to do heavy maintenace on those tools, so
it's a minor issue. But, please add a few lines commenting why you do it,
so it does not get tossed away in the future.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2010-01-11 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 13:58 [PATCH 0 of 2] Add autoconf as a companion tool - 2nd rev Richard Strand
2010-01-11 13:58 ` [PATCH 2 of 2] companion_tools/autoconf: add autoconf tool Richard Strand
2010-01-11 18:48   ` Yann E. MORIN
2010-01-11 19:57     ` Richard Strand
2010-01-11 20:42       ` Richard Strand
2010-01-11 21:04         ` Yann E. MORIN
2010-01-11 20:44       ` Yann E. MORIN [this message]
2010-01-11 20:20     ` Richard Strand
2010-01-11 20:57       ` Yann E. MORIN
2010-01-11 13:58 ` [PATCH 1 of 2] scripts/crosstool-ng: Change overide bin dir Richard Strand
2010-01-11 18:34   ` Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201001112144.09044.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=richard.strand@icomera.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).