This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: glibc 2.1.3
>>>>> Franz Fehringer writes:
>> I've uploaded the 2.1.3 release of glibc to
>>
>> ftp://sourceware.cygnus.com/pub/glibc/releases
>>
>> There you can find the files
>>
>> glibc-2.1.3.tar.bz2 (also .gz)
>> glibc-2.1.2-2.1.3.diff.gz
>> glibc-linuxthreads-2.1.3.tar.gz
>>
>> There is no new crypt add-on since it hasn't changed.
>>
Franz> Does this mean, that glibc-crypt-2.0.111 is current?
No.
Franz> And if so, why not rename it to glibc-crypt-2.1?
From the FAQ:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.5. When linking with the new libc I get unresolved symbols
`crypt' and `setkey'. Why aren't these functions in the
libc anymore?
{UD} The US places restrictions on exporting cryptographic programs and
source code. Until this law gets abolished we cannot ship the cryptographic
functions together with glibc.
The functions are available, as an add-on (see question 1.11). People in the US
may get it from the same place they got GNU libc from. People outside the
US should get the code from ftp.gwdg.de [134.76.11.100] in the directory
pub/linux/glibc, or another archive site outside the USA. The README explains
how to install the sources.
If you already have the crypt code on your system the reason for the failure
is probably that you did not link with -lcrypt. The crypto functions are in
a separate library to make it possible to export GNU libc binaries from the
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
on ftp.gwdg.de you'll find glibc-crypt-2.1.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de