From: Paul Eggert <eggert@cs.ucla.edu>
To: Simon Josefsson <simon@josefsson.org>
Cc: bug-gnulib@gnu.org
Subject: Re: bootstrap: cannot find package name in configure.ac
Date: Wed, 6 Jan 2021 22:00:11 -0800 [thread overview]
Message-ID: <4dc21cb2-b4f5-6152-1c39-6ab85f747df3@cs.ucla.edu> (raw)
In-Reply-To: <87k0spzq58.fsf@latte.josefsson.org>
On 1/6/21 1:55 PM, Simon Josefsson via Gnulib discussion list wrote:
> I'm using the patch below in gsasl, what do you think?
Thanks, looks good to me.
On 1/6/21 3:54 PM, Bernhard Voelker wrote:
> 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):
That stuff was written before autoconf --trace, and it's just a hack.
I'm not sure it's worth spending much time to improve that approach, if
we have something better now.
next prev parent reply other threads:[~2021-01-07 6:00 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
2021-01-07 6:00 ` Paul Eggert [this message]
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=4dc21cb2-b4f5-6152-1c39-6ab85f747df3@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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).