httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Kew <n...@webthing.com>
Subject Re: A Bloat of Libraries
Date Tue, 03 Jan 2006 23:17:02 GMT
On Tuesday 03 January 2006 15:13, Philip M. Gollucci wrote:
> Nick Kew wrote:
> > How about modularised dependencies as a goal for 2.4?
>
> I agree with the idea, but I don't really think theres that manu
> libraries linked in...
>
> I've got a 2.0.55 with mp2, php4, ssl, ruby, python, mod_log_sql
> using a slew of config IfDevines, each server runs only what it needs.
>
> httpd.ssl:
>          libz.so.3 => /lib/libz.so.3 (0x280b6000)
>          libssl.so.4 => /usr/lib/libssl.so.4 (0x280c6000)
>          libcrypto.so.4 => /lib/libcrypto.so.4 (0x280f4000)

Why do any of those have to be linked rather than loaded?

>          libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9
> (0x281e6000)

OK, that's pretty integral to it.

>          libldap-2.2.so.7 => /usr/local/lib/libldap-2.2.so.7 (0x281f8000)
>          liblber-2.2.so.7 => /usr/local/lib/liblber-2.2.so.7 (0x28225000)
>          libdb4.so.0 => /usr/local/lib/libdb4.so.0 (0x28231000)

Again, LoadFile them!

>          libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x282b7000)
>          libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x282d5000)

Borderline cases I guess ...

>          libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x283c2000)

OK, we need apr_dso linked in:-)

>          libm.so.4 => /lib/libm.so.4 (0x283dc000)
>          libcrypt.so.3 => /lib/libcrypt.so.3 (0x283f2000)
>          libc.so.6 => /lib/libc.so.6 (0x2840a000)
>          libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x284e1000)

Libsasl is surely another LoadFile.  And maybe libcrypt.

-- 
Nick Kew

Mime
View raw message