Re: PHP 4 build trouble
| From: | Sascha Schumann | Date: | Fri, 16 Jun 2000 10:53:31 +0000 |
| Subject: | Re: PHP 4 build trouble | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-21497@lists.php.net to get a copy of this message | ||
On Thu, 15 Jun 2000, Lars Hecking wrote:
>
> Hi all,
>
> How can I customise the php 4 build process beyond configure options?
>
> I usually use
>
> $ LDFLAGS=... CPPFLAGS=... ./configure ...
>
> but this method fails utterly with php4 (as ldd .libs/libphp4.so proves).
> I need to add additional -I and -L directives, and the whole build process
> is too opaque to find out which files to modify after running configure.
Give me an example, this has been working for ages.
> Any changes made to config_vars.mk or *.la[i] are not picked up.
You intend to say this:
"config_vars.mk changes are not picked up in Zend/TSRM."
Everything else uses the values found in config_vars.mk.
> Second issue: configure seems to add loads of -L/-R directives
> I just don't want (-R/usr/ucblib is *bad* on Solaris).
It is *not* bad. I've myself verified that on Solaris 2.5.1,
2.6 and 7 and on a couple of other SysV-derivatives.
> Again, which files do I need to modify after running configure?
You should not need to. If you need to pass optional flags,
that probably means that
- you are on an unpopular platform (not Solaris)
- some config.m4s incomplete
In both cases, please send in patches, so that you don't have
to pass additional parameters.
- Sascha