Subject: Re: CVS commit: pkgsrc
To: Todd Vierling <>
From: Johnny C. Lam <>
List: pkgsrc-changes
Date: 03/07/2001 13:07:48
Todd Vierling <> writes:
> On Tue, 6 Mar 2001, Todd Vierling wrote:
> :
> : BTW, I submit that several php3-* modules work Just Fine with interlibrary
> : dependencies, so they *should* work with php4-imap too.  That means there's
> : evidently something wrong in the php4-imap build and/or symbol conflicts
> : between php4, php4-imap, imap-uw, and/or libc.
> Johnny:
> I'm sorry if this came out a bit harsh (as has been told to me by a couple
> people).  I was trying to express a point, probably a little too
> aggressively.
> If you need help addressing these changes, however, please let me know.

Apology accepted.  I don't want to dump egos over a 3rd party package
in NetBSD pkgsrc.  And I'd certainly like to fix things in the right
way and will defer to your greater expertise in these matters.

I think the original apache package from the 1.2.x days had problems
with loadable shared modules as apache needed to explicitly load the
SSL libraries prior to loading  I'll describe the current
problem with apache, php4, and php4-imap as I can best recall:

If the php CGI binary was directly invoked, then there were no
problems.  The problems only arose when using mod_php4.  If the
php.ini file didn't load any shared PHP modules, then apache loaded just fine and could process .php files. The original
php4-imap module ( was dynamically linked against, and  If php.ini loaded, then apache would silently return with no error messages and
no core dump.  If was explicitly loaded (via LoadFile)
before, then apache would refuse to start due to
unresolved symbols in that are defined in expects the client IMAP application to define various
functions that are declared in  This is what lead to
the original workaround of linking libc-client_pic.a directly in to  With this change, apache would load and
correctly process pages with PHP4-IMAP functions.

Something similar also happens with the php4-pgsql module (
Apache won't start unless is explicitly loaded by httpd.conf,
despite the fact the is dynamically linked against

What's the right way to track down the source of the problem?  I'd
like to fix things, but on my 20010206 i386 snapshot system, I'm
having problems getting apache to even start:

so I'm stuck.


     -- Johnny C. Lam <>
        Department of Statistics, Carnegie Mellon University