httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <>
Subject Re: How to link...
Date Tue, 27 Mar 2001 01:18:51 GMT
I've done some work on an early version of Brian's patch but need to do
more.  Basically BeOS is a bit of a PITA for shared libraries as it requires
that ALL symbols be resolved at build time, and if they're not it won't load
the .so, failing with no error. :(

Once I get some more net connectivity (currently in a hotel room in Ghana
with a 21.6 k connection when it decides to connect!) I'll sync up and try
to do more work on it.

FWIW there has been a positive reaction in the Be community to rolling our
own libtool, or at least looking at alternatives so I'll be trying to look
at Jeff's and Brian's sometime soon.

> >"Brian Havard" <> writes:
> >
> >> On Sat, 24 Mar 2001 10:33:13 -0000, David Reid wrote:
> >>
> >> >Brian,
> >> >
> >> >I though OS/2 would have the same problem from previous conversations.
If I
> >> >can help let me know.
> >>
> >> Well, actually I'm pretty much done. I just have to manually add the
> >> missing symbols to the core's .def file until I find a better way to
> >> automate it. I'll wait till Roy finishes his build reorganisation
> >> commiting my build changes though.
> >
> >OS/390 has the same issues.  But we get to use an export-all option on
> >the compile so that we don't have to list symbols explicitly.
> Well, that's a handy one. I've got the hooks taken care of now leaving
> the global variables which rarely change so can be a static list.
> >> If you want to check out the replacement libtool I wrote, you can see
it at
> >>
> >> It's a pretty quick hack but seems to work.
> >
> >There is another one at :)
> >This one understands enough about the Apache code to put the right
> >files in the DLL, and understands enough about OS/390 compile/link
> >options to make it happen.
> Yeah, I looked at it a while ago but it looked a little unwieldy & OS/390
> specific for me.
> >How do you plan to make your libtool available?  I didn't plan
> >anything more fancy than letting it live at the URL listed previously.
> I was thinking of adding it to apr/build/ as it should be fairly easy to
> add support for other platforms and I've managed to keep Apache specific
> stuff out of it.

View raw message