On Tue, 25 Jan 2005, Andrei Zmievski wrote:
On Tue, 25 Jan 2005, Jani Taskinen wrote:
We do link the binaries and libphp*.so without libtool so
why not the shared extensions too. :)
Exactly. Can we do that or is that already done? :)
Already done.
--Jani
--
PHP Internals - PHP Runti
The new bundled libtool seems unhappy on fbsd as well. Trying
--with-gd=shared gives me:
/bin/bash /homes/rasmus/php43/libtool --silent --preserve-dup-deps
--mode=link gcc -DPHP_ATOM_INC -I/homes/rasmus/php43/include
-I/homes/rasmus/php43/main -I/homes/rasmus/php43
-I/homes/rasmus/php43/Zend
Andrei Zmievski wrote:
Thus we'll nuke the libtool usage in linking on Macosx.
Patch to acinclude.m4 for this solution is here:
http://www.php.net/~jani/patches/acinclude.m4.macosx-shared-
modules.patch
(or someone backports the patches from newer libtools to the
bundled file
On Tue, 25 Jan 2005, Jani Taskinen wrote:
> We do link the binaries and libphp*.so without libtool so
> why not the shared extensions too. :)
Exactly. Can we do that or is that already done? :)
- Andrei
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:
On Tue, 25 Jan 2005, Andrei Zmievski wrote:
On Tue, 25 Jan 2005, Jani Taskinen wrote:
I've done a little work on HEAD to make it require autoconf 2.59
and bundle libtool 1.5.10 so this patch might not be necessary there.
But as I don't know if anybody else wishes to start requiring newe
On Tue, 25 Jan 2005, Jani Taskinen wrote:
> I've done a little work on HEAD to make it require autoconf 2.59
> and bundle libtool 1.5.10 so this patch might not be necessary there.
>
> But as I don't know if anybody else wishes to start requiring newer
> autoconf as of PHP 5.1.x, I
On Mon, 24 Jan 2005, Andrei Zmievski wrote:
Thus we'll nuke the libtool usage in linking on Macosx.
Patch to acinclude.m4 for this solution is here:
http://www.php.net/~jani/patches/acinclude.m4.macosx-shared-
modules.patch
(or someone backports the patches from newer libtools to
Thus we'll nuke the libtool usage in linking on Macosx.
Patch to acinclude.m4 for this solution is here:
http://www.php.net/~jani/patches/acinclude.m4.macosx-shared-
modules.patch
(or someone backports the patches from newer libtools to the
bundled files =)
Reason not to
On Thu, 20 Jan 2005, Andrei Zmievski wrote:
What was the reasoning behind the 1.15->1.16 patch for phpize.in? Your
comments say:
- Changed phpize not to require automake and libtool.
- Fixed build system to always use bundled libtool files.
a) To only require autoconf to be installed to be abl
Jani,
What was the reasoning behind the 1.15->1.16 patch for phpize.in? Your
comments say:
- Changed phpize not to require automake and libtool.
- Fixed build system to always use bundled libtool files.
This had an unfortunate effect of building shared extensions on Mac OS
X as .dylib shared lib
10 matches
Mail list logo
