From: David Caldwell <david@porkrind.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 22556@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#22556: 25.0.90; autogen.sh automatic parameter isn't working
Date: Thu, 4 Feb 2016 19:06:12 -0800 [thread overview]
Message-ID: <56B411A4.1090107@porkrind.org> (raw)
In-Reply-To: <vc1t8rring.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On 2/4/16 6:32 PM, Glenn Morris wrote:
> David Caldwell wrote:
>
>> Commit aca31e3815b9bd9c696cf0c74cc4a80ad7e35ec9 seems to have broken
>> './autogen.sh'. It's requiring me to invoke it with the 'autoconf'
>> parameter. A quick peek at the source looks like it should be automatic,
>> but I think there's a bug in the shell code. At least, I needed this
>> change to make the 'autoconf' automatic under bash.
>
> I don't see the issue with bash, but I do with eg dash.
Whoops, you're right: I'm running this on Debian, where /bin/sh is dash.
I forgot to show the symptom in my original bug report, which was:
$ ./autogen.sh
You can now run './autogen.sh autoconf'.
$
>> -for arg in ${*-autoconf}; do
>> +for arg in ${*:-autoconf}; do
>
> The autoconf manual says that this is portable to all shells that
> support functions, so it should be fine, since autogen.sh uses
> functions.
Sorry, were you referring to "${*-autoconf}" or "${*:-autoconf}" being
portable?
-David
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4239 bytes --]
next prev parent reply other threads:[~2016-02-05 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 18:18 bug#22556: 25.0.90; autogen.sh automatic parameter isn't working David Caldwell
2016-02-05 2:32 ` Glenn Morris
2016-02-05 3:06 ` David Caldwell [this message]
2016-02-05 17:41 ` Glenn Morris
2016-02-05 18:06 ` bug#22556: HEAD; " David Caldwell
2016-02-05 22:18 ` bug#22556: 25.0.90; " Paul Eggert
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=56B411A4.1090107@porkrind.org \
--to=david@porkrind.org \
--cc=22556@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=rgm@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.