public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] crypt: Remove manul entry for --enable-crypt Date: Tue, 31 Oct 2023 14:00:19 +0000 (GMT) [thread overview] Message-ID: <20231031140019.2C5F93858D38@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e3397cae92af83ddbf7b9cb89d8c18cb7382fde4 commit e3397cae92af83ddbf7b9cb89d8c18cb7382fde4 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Tue Oct 31 10:59:04 2023 -0300 crypt: Remove manul entry for --enable-crypt Diff: --- manual/install.texi | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/manual/install.texi b/manual/install.texi index a81139780c..ac5310731b 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -256,19 +256,6 @@ configure with @option{--disable-werror}. By default for x86_64, @theglibc{} is built with the vector math library. Use this option to disable the vector math library. -@item --enable-crypt -Install the legacy passphrase-hashing library @file{libcrypt} and the -header file @file{crypt.h}. @file{unistd.h} will declare the function -@code{crypt} regardless of this option. Using this option does not -change the set of programs that may need to be linked with -@option{-lcrypt}; it only means that @theglibc{} will provide that -library. - -This option is for hackers and distributions who may not yet be able to -use libcrypt alternatives such as libxcrypt and need this legacy -implementation as a temporary workaround. Note that libcrypt may be -removed in a future release. - @item --disable-scv Disable using @code{scv} instruction for syscalls. All syscalls will use @code{sc} instead, even if the kernel supports @code{scv}. PowerPC only.
reply other threads:[~2023-10-31 14:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231031140019.2C5F93858D38@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@sourceware.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: linkBe 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).