Re: always building cgi...
| From: | (Stig Sæther Bakken) | Date: | Wed, 11 Apr 2001 18:43:00 +0000 |
| Subject: | Re: always building cgi... | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-51459@lists.php.net to get a copy of this message | ||
[Sascha Schumann <sascha@schumann.cx>]
> > Sascha, what symbols can sneak in to break linking? A few examples I
> > can test with would be nice.
>
> As other people on this list have mentioned, building
> --with-apxs illustrates the breakage.
>
> The chosen SAPI module (i.e. sapi/apache/libsapi.la) is part
> of libphp4.la. Usually, the SAPI module contains calls to
> server-specific APIs which are resolved upon loading the SAPI
> module into the web-server. Those external symbols cannot be
> found (of course) during creating the CGI which is built
> using libphp4.la.
Okay, what about making libphp4.la contain everything but libsapi.la,
and make a new final target including libsapi.la called
libphp4_xxx.la, where xxx is the sapi module used.
With some more minor restructuring, we can then let people build _all_
sapi modules in one go if they like.
- Stig
--
Stig Sæther Bakken <ssb@fast.no>
Fast Search & Transfer ASA, Trondheim, Norway