RE: [PHP-DEV] process in README.SELF-CONTAINED-EXTENSIONS broken?

I dunno the solution to the warnings from phpize, (since i havent figured a way to fix that), But I think they are benign warnings. The error message... "You should update your `aclocal.m4' by running aclocal." seems bogus. It would be great if someone here can comment on it. Anycase, you need to pass "--php-config=/path/to/php-config" to configure. --Roshan > -----Original Message----- > From: Brian Lalor > [mailto:blalor+dated+1032286275.8fc6df@ithacabands.org] > Sent: Thursday, September 12, 2002 11:28 AM > To: php-dev@lists.php.net > Subject: [PHP-DEV] process in README.SELF-CONTAINED-EXTENSIONS broken? > > > > I just grabbed PHP from CVS and tried to go through the > procedure outlined in > README.SELF-CONTAINED-EXTENSIONS and found that it doesn't > work. Can someone > help? I'm looking at revision 1.10 of the README. > > The php4 module's checked out into my ~/devel directory. So > under CONVERTING > AN EXISTING EXTENSION, I do > mkdir /tmp/newext > cd /tmp/newext > cp -rp ~/devel/php4/ext/sockets/* . > phpize > > phpize gives some warnings: > aclocal: macro `AC_ADD_LIBPATH' defined in > acinclude.m4 but never used > aclocal: macro `AC_ADD_LIBRARY' defined in > acinclude.m4 but never used > aclocal: macro `AC_ADD_LIBRARY_WITH_PATH' defined in > acinclude.m4 but never used > aclocal: macro `AC_ADD_INCLUDE' defined in > acinclude.m4 but never used > You should update your `aclocal.m4' by running aclocal. > > I ran aclocal, which gave the same output as phpize, save for > the last line; > finally: > ./configure > > configure dies with: > configure: error: can not find sources in . or .. > > I've tried running buildconf and configure in the cvs working > directory, but > still no dice. Can anyone help? > > B > > -- > Brian Lalor > blalor@ithacabands.org > blalor@jabber.ithacabands.org > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php >