I decided to just give up on trying to have a modern PHP Source
development environment and re-compiled the exact same version (-r
5_0) as my webhost has, so that I could just bypass the whole issue of
getting configure to read/write the paths I want to.
My "Hello World" extension now works!
I would like, at some point, to understand how configure actually
works with regard to using multiple include/lib dirs.
The closest I could come to that was when I'd get as far as compiling
my extension and it would blow up with a bunch of errors about UChar
and stuff like that...
Maybe the macros for extensions changed with the ICU addition? [shrug]
Anyway, y'all will hopefully breathe a sigh of relief that I won't
post as much.
--
Like Music?
http://l-i-e.com/artists.htm
Richard Lynch wrote:
I decided to just give up on trying to have a modern PHP Source
development environment and re-compiled the exact same version (-r
5_0) as my webhost has, so that I could just bypass the whole issue of
getting configure to read/write the paths I want to.
-r 5_1 should be fine as well. autoconf-wise there haven't been that
many changes.
-Rasmus
Richard Lynch wrote:
I decided to just give up on trying to have a modern PHP Source
development environment and re-compiled the exact same version (-r
5_0) as my webhost has, so that I could just bypass the whole issue
of
getting configure to read/write the paths I want to.-r 5_1 should be fine as well. autoconf-wise there haven't been that
many changes.
The problem is that configure keeps seeming to find /usr/local/* for
one thing or another, and then it's not running/compiling the things I
want...
With 5.0, when it finds stuff in /usr/local/* it's the same stuff I
wanted it to find in my home dir anyway, so all is good.
When I tried -r 5_1, I just ended up with a mess.
I might give it another shot after I finish up my extension, since I'd
want to do that for testing anyway.
PS
I still have to hand edit my homedir phpize to rip out the exit 1
calls in the autoconf/autoheader tests.
export PHP_AUTOCONF=/usr/local/bin/autoconf213
export PHP_AUTOHEADER=/usr/local/bin/autoheader213
just don't seem to be working for me, to get past those tests.
That really don't seem "right" to me... Though, obviously, I'm not
competent enough to say it's "wrong" either.
--
Like Music?
http://l-i-e.com/artists.htm
When you install PHP, use the right prefix. When you phpize
something, use the --with-php-config=PREFIX/bin/php-config
with the generated configure, that way you get to use the right
include paths.
--Jani
Richard Lynch wrote:
I decided to just give up on trying to have a modern PHP Source
development environment and re-compiled the exact same version (-r
5_0) as my webhost has, so that I could just bypass the whole issue
of
getting configure to read/write the paths I want to.-r 5_1 should be fine as well. autoconf-wise there haven't been that
many changes.The problem is that configure keeps seeming to find /usr/local/* for
one thing or another, and then it's not running/compiling the things I
want...With 5.0, when it finds stuff in /usr/local/* it's the same stuff I
wanted it to find in my home dir anyway, so all is good.When I tried -r 5_1, I just ended up with a mess.
I might give it another shot after I finish up my extension, since I'd
want to do that for testing anyway.PS
I still have to hand edit my homedir phpize to rip out the exit 1
calls in the autoconf/autoheader tests.export PHP_AUTOCONF=/usr/local/bin/autoconf213
export PHP_AUTOHEADER=/usr/local/bin/autoheader213just don't seem to be working for me, to get past those tests.
That really don't seem "right" to me... Though, obviously, I'm not
competent enough to say it's "wrong" either.
--
Give me your money at @ http://pecl.php.net/wishlist.php/sniper
Donating money may make me happier and friendlier for a limited period!
Death to all 4 letter abbreviations starting with P!