You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Marc Slemko <ma...@znep.com> on 1998/07/12 19:13:44 UTC

config/2590: Linking of modules libs (fwd)

We need to link things in support against the extra libraries we figure
out automatically, since in general we may need things like libcrypt,
lib*db*, etc.

The only thing we could do is not include libs specified in EXTRA_LIBS.
I'm not thrilled with that, however, since it means that if users do need
some extra library to make it work right, they can't compile stuff in
support.  

So my suggestion would be to just close the PR and say we don't have much
choice, and it doesn't really hurt too much.

---------- Forwarded message ----------
Date: 12 Jul 1998 04:22:45 -0000
From: Stephen Webb <sp...@dodds.net>
To: apbugs@hyperreal.org
Subject: config/2590: Linking of modules libs


>Number:         2590
>Category:       config
>Synopsis:       Linking of modules libs
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Jul 11 21:30:00 PDT 1998
>Last-Modified:
>Originator:     spidey@dodds.net
>Organization:
apache
>Release:        1.3.0
>Environment:
Linux viper.webb.dodds.net 2.0.34 #1 Fri May 8 16:05:57 EDT 1998 i586 unknown
Redhat 5.1
>Description:
I have compiled apache 1.3.0 with php 3.0.1 and suexec and I noticed the suexec
 had  this as it's ldd output:
[spidey@viper apache_1.3.0]$ ldd src/support/suexec
        libm.so.6 => /lib/libm.so.6 (0x40005000)
        libdl.so.2 => /lib/libdl.so.2 (0x4001e000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x40021000)
        libdb.so.2 => /lib/libdb.so.2 (0x4004e000)
        libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x4005e000)
        libttf.so.2 => /usr/lib/libttf.so.2 (0x40064000)
        libgd.so.1 => /usr/lib/libgd.so.1 (0x4007a000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x400b1000)
        libpq.so.1 => /usr/lib/libpq.so.1 (0x400bf000)
        libz.so.1 => /usr/lib/libz.so.1 (0x400ca000)
        libc.so.6 => /lib/libc.so.6 (0x400d8000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)

It is not needed to link suexec or any or the other binarys in src/support to
any of the libs needed for extra modules.
>How-To-Repeat:
Just Compile php 3.0.1 into apache using there Quick method in the INSTALL file
>Fix:
When the configure makes the Makefile for the support dir do not include the 
extra module libs
>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/2590: Linking of modules libs (fwd)

Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Marc Slemko wrote:
> 
> We need to link things in support against the extra libraries we
> figure out automatically, since in general we may need things like
> libcrypt, lib*db*, etc.
> 
> The only thing we could do is not include libs specified in
> EXTRA_LIBS. I'm not thrilled with that, however, since it means that
> if users do need some extra library to make it work right, they can't
> compile stuff in support.
> 
> So my suggestion would be to just close the PR and say we don't have
> much choice, and it doesn't really hurt too much.

That's exactly how I was going to respond to this.  I prefer
the Makefile consistency at this point over perfect correctness
no-more-no-less for every buildable item.

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>