From: Zack Weinberg <zackw@panix.com>
To: Rical Jasan <rj@2c3t.io>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Nikos Mavrogiannopoulos <nmav@redhat.com>
Subject: Re: [PATCH v2] New configure option --disable-crypt.
Date: Mon, 23 Apr 2018 15:22:00 -0000 [thread overview]
Message-ID: <CAKCAbMiDhRi3o8d-C8rNkMK4OubQETHhq+TGYYQQNjt1j-AKmw@mail.gmail.com> (raw)
In-Reply-To: <0e8ffb1b-afd4-ab6e-04ac-bf5e954833ab@2c3t.io>
On Wed, Apr 18, 2018 at 5:05 PM, Rical Jasan <rj@2c3t.io> wrote:
> It looks like --runstatedir slipped in to the generated configure. I'm
> not opposed to it in general, and I don't think it's used anywhere
> anyway, but it doesn't seem related, and isn't mentioned. I think it's
> an artifact of autotools versions.
Yeah, it is. I have Debian's autoconf 2.69, which has --runstatedir
backported from autoconf trunk. I can hand-edit that back out if
people think it's worth avoiding the churn.
> I believe --disable-crypt should also be added to install.texi (and
> INSTALL regenerated, IIRC).
Will fix.
> There is also an entire chapter in the manual devoted to these
> functions. It does convey, "Don't do this," to an extent -- in a number
> of ways -- but I'm open to suggestions for improvement, particularly in
> light of this patch. It's a pretty short chapter.
Yeah, I'm just looking over that chapter now.
zw
prev parent reply other threads:[~2018-04-23 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 18:34 Zack Weinberg
2018-04-18 20:41 ` Andreas Schwab
2018-04-23 15:29 ` Zack Weinberg
2018-04-18 21:05 ` Rical Jasan
2018-04-23 15:22 ` Zack Weinberg [this message]
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=CAKCAbMiDhRi3o8d-C8rNkMK4OubQETHhq+TGYYQQNjt1j-AKmw@mail.gmail.com \
--to=zackw@panix.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nmav@redhat.com \
--cc=rj@2c3t.io \
/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).