On Thu, Jan 29, 2004 at 02:07:28PM +0100, Sascha Schumann wrote:
> On Thu, 29 Jan 2004, Patrick Welche wrote:
>
> > On Fri, Jan 23, 2004 at 08:51:16AM +0100, Sascha Schumann wrote:
> > > If you want to propose modifications to the current build
> > > ch
On Fri, Jan 23, 2004 at 08:51:16AM +0100, Sascha Schumann wrote:
> If you want to propose modifications to the current build
> chain, feel free to post a patch.
Enclosed is an even nicer patch. I shouldn't have mentioned the "cat"
warning in the previous posting - it has nothing to do with
On Fri, Jan 23, 2004 at 08:51:16AM +0100, Sascha Schumann wrote:
> > The above still stands. I would call your use of the autotools
> > unorthodox.
>
> The problem with a number of autotools is that they are
> unsuitable for large projects which contain a huge number of
> independent m
On Thu, Jan 22, 2004 at 04:51:43PM +0200, Jani Taskinen wrote:
>
> There's nothing wrong in this. If your autoconf/aclocal/etc.
> tools are installed correctly, buildconf works fine.
>
> Please use the snapshots if you don't know what you're doing.
:-) I have to smile otherwise I
On Thu, Jan 22, 2004 at 01:06:11PM +0200, Jani Taskinen wrote:
>
> Yes, you need libtool 1.4.3. (no, 1.5 is not backwards compatible)
There is still something strange with buildconf:
% make -n -s -f build/build.mk AMFLAGS= ZENDDIR=Zend
build/buildcheck.sh buildmk.stamp
echo makefile_am_files
On Wed, Jan 21, 2004 at 10:07:13PM +0200, Jani Taskinen wrote:
>
> Do fresh checkout of 'php5' module. You'll get all correct
> files then, no need to checkout ZendEngine2 separately..
I'm amazed how much that helped.. Now there is just the following buglet:
buildconf: libtool version
I just cvs update -A a php4 src tree to get php5 (had to checkout ZendEngine2),
and assume that the next thing to do is run buildconf. One thing: after
the dance of mv ZendEngine2 Zend, future cvs updates are going to miss
ZendEngine2 and this will no longer be updated - would a symlink be a better
