The following reply was made to PR config/2372; it has been noted by GNATS.
From: Dean Gaudet <[EMAIL PROTECTED]> To: Steve Baur <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: config/2372: If libcrypt is installed, it will be used even if compiling for libc5 Date: Sun, 7 Jun 1998 22:53:17 -0700 (PDT) On 8 Jun 1998, Steve Baur wrote: > + doing sanity check on compiler and options > ld: warning: libc.so.6, needed by /usr/lib/libcrypt.so, may conflict with > libc.so.5 > > The Linux test for detecting -lcrypt is too aggressive. I have all > compiler options set to values which worked for building against libc5 > on a libc6 system (it worked in 1.2.6), except that -lcrypt gets > detected (it's there) even when I try to make a libc5 binary. Actually, no, I'd be more tempted to say that if your compiler can find a libcrypt which doesn't work with the settings you gave, then that's a problem with the settings you gave. There's nothing we can do to work around broken compiler settings... > Libc6 is not ready for prime time, I'd suggest forcing the installer > to put -lcrypt in one of the Configuration flags. I would have agreed with you three months ago. But redhat's 2.0.7-13 has been just fine to me... We won't remove the libcrypt autodetection. It's a FAQ for folks building 1.2 on redhat, it wastes our time dealing with people who don't add -lcrypt. This is a transitional period, yeah it hurts. Six months from now we'd be flogging a dead horse by still requiring folks to add -lcrypt. Dean
