Subject: Re: why is there no libgcc.so
To: Caffeinate The World <mochaexpress@yahoo.com>
From: Charles M. Hannum <root@ihack.net>
List: port-alpha
Date: 03/07/2001 22:42:35
On Wed, Mar 07, 2001 at 10:35:39PM -0800, Caffeinate The World wrote:
>
> --- "Charles M. Hannum" <root@ihack.net> wrote:
> >
> > On Wed, Mar 07, 2001 at 10:17:27PM -0800, Jason R Thorpe wrote:
> > > On Wed, Mar 07, 2001 at 09:36:18PM -0800, Caffeinate The World
> > wrote:
> > >
> > > > thanks for the reply todd. in case anyone tried to get Sablot
> > 0.51 to
> > > > work under PHP 4.0.5-dev on NetBSD, you'll have to create
> > libgcc.so and
> > > > link with -lgcc in PHP4 to get it to work properly. Otherwise
> > you'll
> > > > get an undefined symbol "__builtin_XXXX" when you restart Apache
> > (for
> > > > php mod compiled from source not package).
> > >
> > > Uh, that sounds like a bug in the PHP4 build process.
> >
> > No, it sounds like a bug in the Apache build process. Programs that
> > load modules *have* to be linked with --export-dynamic and
> > --force-archive to make sure all the symbols are exported.
>
> i don't have any problems with any modules with either PHP4 or Apache.
> I've only encountered this when linking PHP4 with Sablotron.
That certainly does not mean the Apache build process isn't broken. It
just means you got lucky with other modules.