bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: bootstrap: cannot find package name in configure.ac
Date: Thu, 7 Jan 2021 00:54:19 +0100	[thread overview]
Message-ID: <f6b4052b-392d-c2e5-3a57-e59583b08441@bernhard-voelker.de> (raw)
In-Reply-To: <87k0spzq58.fsf@latte.josefsson.org>

On 1/6/21 10:55 PM, Simon Josefsson via Gnulib discussion list wrote:
> Hi.  I'm setting GNU SASL up for git-version-gen and bootstrap, and
> noticed that bootstrap doesn't handle git-version-gen well.  See:
> 
> jas@latte:~$ cat>configure.ac
> AC_INIT([GNU SASL],
>         m4_esyscmd([build-aux/git-version-gen .tarball-version]),
>         [bug-gsasl@gnu.org],
>         [gsasl])
> jas@latte:~$ ~/src/gnulib/build-aux/bootstrap 
> /home/jas/src/gnulib/build-aux/bootstrap: cannot find package name in configure.ac
> jas@latte:~$ 

The existing 'bootstrap' works if the AC_INIT command is written in
one (well, long) line.
BTW: 'autoupdate' would exactly do that: squash the whole command into
one line.

And instead of adding yet another way to do the same job, shouldn't the
existing code better be fixed?  At least it obviously doesn't do what the
comments above the sed script say (bootstrap:186):

  # Prefer a non-empty tarname (4th argument of AC_INIT if given), else
  # fall back to the package name (1st argument with munging)

FWIW there's a final dot '.' missing in that comment.

Have a nice day,
Berny


  reply	other threads:[~2021-01-06 23:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 21:55 bootstrap: cannot find package name in configure.ac Simon Josefsson via Gnulib discussion list
2021-01-06 23:54 ` Bernhard Voelker [this message]
2021-01-07  6:00 ` Paul Eggert
2021-01-08 10:53   ` Simon Josefsson via Gnulib discussion list

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=f6b4052b-392d-c2e5-3a57-e59583b08441@bernhard-voelker.de \
    --to=mail@bernhard-voelker.de \
    --cc=bug-gnulib@gnu.org \
    --cc=simon@josefsson.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.
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).