Re: [PHP4BETA] modular php build on unix
| From: | Egon Schmid | Date: | Wed, 01 Sep 1999 19:56:00 +0000 |
| Subject: | Re: [PHP4BETA] modular php build on unix | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-3981@lists.php.net to get a copy of this message | ||
Hi Greg,
Gergely Madarasz wrote:
> I checked php4 to build a debian package from it and I have concerns
> regarding the shared extension build of the packages...
> I see the xml module can be build as a shared extension, but the build
> script builds a libphpext_xml.so.0.0.0 with a soname libphpext_xml.so.0,
> while, I guess, the name of the module should be xml.so and there is no
> need for a soname. This is not a library, to be linked against, just a
> module to be loaded. The flag -avoid-version to libtool will disable the
> version extension in the file generated, but the soname will remain. I
> guess that won't be such a big problem.
>
> BTW I don't quite get what this make does. First it compiles xml.c to
> xml.o without libtool, creates libphpext_xml.a, then invokes libtool,
> compiles xml.c again, now twice (xml.o and xml.lo), and then creates both
> the .a and the .sa archives. I don't know why the first compile happens,
> the second can be disabled by disabling static libraries in libtool.
>
> Additionally if these things are settled, I'm willing to help making the
> other extensions, just tell me how to do it what problems I might
> encounter :)
You know I use most time Debian. But I did a compile on RedHad 6.0
today. To be able to do the ./buildconf I installed libtool-1.3.3. Then
I noticed that AM_PROG_LIBTOOL is not in the library. So I commented it
out in configure.in.in. The build succeeded with this warning:
"ext/xml/Makefile.am:8 Library used but `LIBTOOL' not defined in
`configure.in'.
Stig are there some RPMs for libtool, autoconf, and automake?
-Egon