public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Zack Weinberg" <zack@owlfolio.org>
Cc: carlos@redhat.com, alx@kernel.org, libc-alpha@sourceware.org
Subject: Re: [patch v4] manual: add syscall list
Date: Thu, 23 May 2024 15:38:45 -0400	[thread overview]
Message-ID: <xncypc71yy.fsf@greed.delorie.com> (raw)
In-Reply-To: <b2792b30-077c-46f8-ab42-b78a28bc1d4e@app.fastmail.com> (zack@owlfolio.org)

"Zack Weinberg" <zack@owlfolio.org> writes:
>> +man_pages_version=6.8
>> +
>> +AC_ARG_WITH([man-pages],
>> +	    AS_HELP_STRING([--with-man-pages=VERSION],
>> +			   [tie manual to a specific man-pages version]),
>> +	    [man_pages_version=$withval],
>> +	    [])
>> +AC_SUBST(man_pages_version)
>> +
>>  AC_ARG_ENABLE([sanity-checks],
>>  	      AS_HELP_STRING([--disable-sanity-checks],
>>  			     [really do not use threads (should not be used except in 
>
> This is fine as is.  I might suggest a tiny change: instead of
> setting the default value for man_pages_version above the AC_ARG_WITH,
> set it in the action-if-not-given:

I started that way, but moved it out so it would be more obvious where
to change the value when the time comes.  This is the same thing we do
with the minimum kernel version, although in that case the default value
is spread across target-specific files.

> Also, I wonder if it makes sense to tie the default here to the
> default for --enable-kernel, assuming there is one.

--enable-kernel sets a minimum kernel version, whereas the man pages is
typically going to be the latest (maximum) version.

>> -if test ${ac_cv_prog_cxx_cxx11+y}
>> +if test ${ac_cv_prog_cxx_11+y}
>>  then :
> ...
>
> This looks like you didn’t use the same version of Autoconf as the
> last person to update configure.ac.  As I understand it we’re trying
> to stick to a constant version.  Check with Joseph Myers for what you
> should be using.

I used verison 2.71 (as noted in configure) right from the GNU ftp site.

The last time this line was changed, it was from
c6cb8783b5fb5896cb63fe9008b6a33351f3c777 which changed us from autoconf
2.69 to 2.71.

It turns out Fedora has added a patch to 2.71 that makes the '-' side of
the changes noted; which means that we can't use Fedora's autoconf if the
rule is (as documented) "GNU autoconf 2.71 (exactly)".

Or we need to change the rules.

  "If you change any of the 'configure.ac' files you will also need

     * GNU 'autoconf' 2.71 (exactly)"


  reply	other threads:[~2024-05-23 19:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 20:52 manual: add syscall list appendix DJ Delorie
2024-05-16  5:02 ` Florian Weimer
2024-05-16 11:44   ` Carlos O'Donell
2024-05-16 12:06     ` Florian Weimer
2024-05-16 13:37     ` Alejandro Colomar
2024-05-16 14:52       ` Carlos O'Donell
2024-05-16 15:03         ` Alejandro Colomar
2024-05-16 17:57       ` DJ Delorie
2024-05-16 17:55     ` DJ Delorie
2024-05-16 21:08       ` Alejandro Colomar
2024-05-17 13:21       ` Carlos O'Donell
2024-05-17 15:31         ` DJ Delorie
2024-05-17 19:16           ` Carlos O'Donell
2024-05-20 21:43             ` [patch v2] manual: add syscall list DJ Delorie
2024-05-20 22:10               ` Alejandro Colomar
2024-05-21  1:12                 ` DJ Delorie
2024-05-21 10:22                   ` Alejandro Colomar
2024-05-21 17:16                     ` DJ Delorie
2024-05-21 20:04                 ` [patch v3] " DJ Delorie
2024-05-22 19:07                   ` Carlos O'Donell
2024-05-22 19:40                     ` DJ Delorie
2024-05-22 19:41                     ` [patch v4] " DJ Delorie
2024-05-22 19:42                       ` DJ Delorie
2024-05-22 20:54                       ` Florian Weimer
2024-05-22 21:00                         ` Florian Weimer
2024-05-22 21:26                         ` DJ Delorie
2024-05-23  7:31                           ` Florian Weimer
2024-05-23  8:49                             ` Andreas Schwab
2024-05-22 22:45                       ` DJ Delorie
2024-05-22 23:12                       ` Alejandro Colomar
2024-05-23 16:59                       ` Zack Weinberg
2024-05-23 19:38                         ` DJ Delorie [this message]
2024-05-23 19:41                           ` Zack Weinberg
2024-05-23 19:46                             ` DJ Delorie
2024-05-23 19:51                             ` Joseph Myers
2024-05-23 21:18                         ` Alejandro Colomar
2024-05-16 17:37   ` manual: add syscall list appendix DJ Delorie
2024-05-16 17:55     ` Joe Simmons-Talbott

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=xncypc71yy.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=alx@kernel.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zack@owlfolio.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).