mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-18 19:29:21 +01:00
glibc: Disable obsolete libcrypt implementation
I've not bothered to write an explanation for --disable-crypt because it will likely be the default of Glibc-2.38, then we may drop it from the command lines.
This commit is contained in:
parent
ce9ec4f126
commit
bbfb090d2a
@ -91,6 +91,7 @@ cd build</userinput></screen>
|
||||
--build=$(../scripts/config.guess) \
|
||||
--enable-kernel=&min-kernel; \
|
||||
--with-headers=$LFS/usr/include \
|
||||
--disable-crypt \
|
||||
libc_cv_slibdir=/usr/lib</userinput></screen>
|
||||
|
||||
<variablelist>
|
||||
|
@ -79,6 +79,7 @@ cd build</userinput></screen>
|
||||
--enable-kernel=&min-kernel; \
|
||||
--enable-stack-protector=strong \
|
||||
--with-headers=/usr/include \
|
||||
--disable-crypt \
|
||||
libc_cv_slibdir=/usr/lib</userinput></screen>
|
||||
|
||||
<variablelist>
|
||||
@ -489,7 +490,7 @@ mkdir -pv /etc/ld.so.conf.d</userinput></screen>
|
||||
<seg>ld-linux-x86-64.so.2, ld-linux.so.2,
|
||||
libBrokenLocale.{a,so}, libanl.{a,so},
|
||||
libc.{a,so}, libc_nonshared.a, libc_malloc_debug.so,
|
||||
libcrypt.{a,so}, libdl.{a,so.2}, libg.a, libm.{a,so},
|
||||
libdl.{a,so.2}, libg.a, libm.{a,so},
|
||||
libmcheck.a, libmemusage.so, libmvec.{a,so}, libnsl.so.1,
|
||||
libnss_compat.so, libnss_dns.so, libnss_files.so, libnss_hesiod.so,
|
||||
libpcprofile.so, libpthread.{a,so.0},
|
||||
@ -795,16 +796,6 @@ mkdir -pv /etc/ld.so.conf.d</userinput></screen>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="libcrypt">
|
||||
<term><filename class="libraryfile">libcrypt</filename></term>
|
||||
<listitem>
|
||||
<para>The cryptography library</para>
|
||||
<indexterm zone="ch-system-glibc libcrypt">
|
||||
<primary sortas="c-libcrypt">libcrypt</primary>
|
||||
</indexterm>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="libdl">
|
||||
<term><filename class="libraryfile">libdl</filename></term>
|
||||
<listitem>
|
||||
|
Loading…
Reference in New Issue
Block a user