config/2372: If libcrypt is installed, it will be used even if compiling for libc5 (fwd)

[Marc Slemko <ma...@znep.com>]

<sigh>

I am tempted to say "tough, if you are going to do things like that it is
your problem."  We can _not_ remove the -lcrypt test.

At most, we could add some option to prevent any automated tests from
adding any flags to the compile or link lines.

---------- Forwarded message ----------
Date: 8 Jun 1998 00:28:01 -0000
From: Steve Baur <st...@calag.com>
To: apbugs@hyperreal.org
Subject: config/2372: If libcrypt is installed, it will be used even if compiling for libc5


>Number:         2372
>Category:       config
>Synopsis:       If libcrypt is installed, it will be used even if compiling for libc5
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Jun  7 17:30:00 PDT 1998
>Last-Modified:
>Originator:     steve@calag.com
>Organization:
apache
>Release:        1.3.0
>Environment:
Linux 2.0.34, Glibc 2.0.7-pre2 as primary libc, Linux libc5 installed
as secondary libc.  Hand configuring in src/ with the traditional
method of modifying Configuration and running ./Configure.
>Description:
+ 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.
>How-To-Repeat:
Attempt to build apache on a Linux system with both libc5 and libc6
installed and attempt to build against libc5.
>Fix:
Libc6 is not ready for prime time, I'd suggest forcing the installer
to put -lcrypt in one of the Configuration flags.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]

Re: config/2372: If libcrypt is installed, it will be used even if compiling for libc5 (fwd)

[Dean Gaudet <dg...@arctic.org>]

If you want to code that and test it, go for it.  I don't particularly
care.  As I mentioned in the text for PR#2372 this is a configuration that
very few people will use. 

redhat-5.x as shipped support libc5-linked applications.  But you can't
build libc5-linked applications -- they don't include the libc5 header
files, for example.

It's just a rats nest to support both universes on the same machine.  I've
tried. 

Dean

On Mon, 8 Jun 1998, Marc Slemko wrote:

> Hmm.  The other thing we could do is try with their settings to compile
> something that has a reference to crypt() in without -lcrypt; if it works,
> cool, if not try adding -lcrypt and seeing if it works.

Re: config/2372: If libcrypt is installed, it will be used even if compiling for libc5 (fwd)

[Marc Slemko <ma...@worldgate.com>]

Hmm.  The other thing we could do is try with their settings to compile
something that has a reference to crypt() in without -lcrypt; if it works,
cool, if not try adding -lcrypt and seeing if it works.

On Sun, 7 Jun 1998, Marc Slemko wrote:

> <sigh>
> 
> I am tempted to say "tough, if you are going to do things like that it is
> your problem."  We can _not_ remove the -lcrypt test.
> 
> At most, we could add some option to prevent any automated tests from
> adding any flags to the compile or link lines.
> 
> ---------- Forwarded message ----------
> Date: 8 Jun 1998 00:28:01 -0000
> From: Steve Baur <st...@calag.com>
> To: apbugs@hyperreal.org
> Subject: config/2372: If libcrypt is installed, it will be used even if compiling for libc5
> 
> 
> >Number:         2372
> >Category:       config
> >Synopsis:       If libcrypt is installed, it will be used even if compiling for libc5
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       medium
> >Responsible:    apache
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   apache
> >Arrival-Date:   Sun Jun  7 17:30:00 PDT 1998
> >Last-Modified:
> >Originator:     steve@calag.com
> >Organization:
> apache
> >Release:        1.3.0
> >Environment:
> Linux 2.0.34, Glibc 2.0.7-pre2 as primary libc, Linux libc5 installed
> as secondary libc.  Hand configuring in src/ with the traditional
> method of modifying Configuration and running ./Configure.
> >Description:
> + 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.
> >How-To-Repeat:
> Attempt to build apache on a Linux system with both libc5 and libc6
> installed and attempt to build against libc5.
> >Fix:
> Libc6 is not ready for prime time, I'd suggest forcing the installer
> to put -lcrypt in one of the Configuration flags.
> >Audit-Trail:
> >Unformatted:
> [In order for any reply to be added to the PR database, ]
> [you need to include <ap...@Apache.Org> in the Cc line ]
> [and leave the subject line UNCHANGED.  This is not done]
> [automatically because of the potential for mail loops. ]
> 
> 
>