RE: Where should libc-lock.h be installed

["Wright, Shayne (SAHO)" <Shaynew@saho.org>]

Hello

I used glibc-crypt-2.0.6.tar.gz and glibc-linuxthreads-2.1.1.tar.gz as
add-ons - the most recent versions available on ftp.gnu.org. Where can I
find glibc-crypt-2.1.1.tar.gz?
Once I obtain the 2.1 version, is there a way I can just recompile and
install glibc-crypt, or is it necessary to completely recompile and
reinstall glibc? Should I also be looking for the
glibc-localedata-2.1.1.tar.gz? I did not use this add-on as localedata
appears to now be distributed as part of glibc-2.1.1.

Thanks for the advice,
Take Care,
Shayne

> -----Original Message-----
> From:	Andreas Jaeger [SMTP:aj@arthur.rhein-neckar.de]
> Sent:	Tuesday, June 22, 1999 11:57 AM
> To:	Wright, Shayne (SAHO)
> Cc:	'glibc-linux@ricardo.ecn.wfu.edu'
> Subject:	Re: Where should libc-lock.h be installed
> 
> >>>>> SAHO  writes:
> 
>  > Hello
> 
>  > I have just finished upgrading from glibc-2.0.6 to glibc-2.1.1. For the
> most
>  > part everything went fine, make and make check completed without error,
>  > however make install failed. The problem was caused by the
> crypt_utils.d
>  > file in the glibc-build/md5-crypt directory. The crypt_utils.d file was
>  > looking for the libc-lock.h file in /usr/include, but the header file
> is
>  > actually installed in /usr/include/bits/libc-lock.h. After I changed
> the
>  > reference in crypt_utils.d to the /usr/include/bits directory; make
> install
>  > completed successfully.
> 
>  > I configured glibc-2.1.1 with --prefix=/usr and with the crypt and
>  > linuxthreads addons.
> 
>  > Now my question is what caused the problem and which situation is
> wrong: the
>  > reference to /usr/include/libc-lock.h in crypt_utils.d, or installing
>  > libc-lock.h in /usr/include/bits.
> 
> Which crypt version are you using?  You should use the 2.1 version!
> 
> Andreas
> -- 
>  Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
>   for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de