Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Jani Taskinen
Yes, they are different things. I committed a bit better fix in CVS now. Remember to run ./cvsclean && ./buildconf after update. $host_alias will not be empty now. If it is, configure will stop at that. --Jani On Thu, 6 Jan 2005, Brad House wrote: ok, so they _are_ different nam

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Andrei Zmievski
On Thu, 06 Jan 2005, Brad House wrote: > I think you lost me somewhere > > The module still gets compiled as myext.so > PHP_SHLIB_SUFFIX does not affect that at all (perhaps > you're saying it's supposed to but did not?) > > The PHP_SHLIB_SUFFIX affects the autoconf macro PHP_SETUP_OPENSSL

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Brad House
Are you sure we're talking about the same constant here. The one in particular I'm talking about is 100% in the build system. I do not believe it is exported as a define into the actual code... Though I could be wrong. Having PHP_SHLIB_SUFFIX is confusing though, as MacOSX differentiates shared li

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Brad House
ok, so they _are_ different names then: In the auto-scripts it's SHLIB_SUFFIX_NAME as per this that get's pulled in as an actual PHP constant. main/build-defs.h.in:91:#define PHP_SHLIB_SUFFIX "@SHLIB_SUFFIX_NAME@" main/main.c:1206: REGISTER_MAIN_STRINGL_CONSTANT("PHP_SHLIB_SUFFIX", PHP_SHLIB_SUFF

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Andrei Zmievski
On Thu, 06 Jan 2005, Brad House wrote: > Are you sure we're talking about the same constant here. The one > in particular I'm talking about is 100% in the build system. I do > not believe it is exported as a define into the actual code... > Though I could be wrong. Yes. The PHP_SHLIB_SUFFIX_NAME

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Brad House
I think you lost me somewhere The module still gets compiled as myext.so PHP_SHLIB_SUFFIX does not affect that at all (perhaps you're saying it's supposed to but did not?) The PHP_SHLIB_SUFFIX affects the autoconf macro PHP_SETUP_OPENSSL() specifically on MacOSX (it may very well affect othe

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-06 Thread Andrei Zmievski
On Tue, 04 Jan 2005, Brad House wrote: > Just tried to phpize an extension, and it appears as though > there is a problem on MacOSX. PHP_SHLIB_SUFFIX defaults to .so > because a check is run on $host_alias, which is set to "". Just to make sure: we do want PHP_SHLIB_SUFFIX to be set to .so on Mac

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-05 Thread Brad House
[EMAIL PROTECTED] ~ $ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

Re: [PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-04 Thread Jani Taskinen
How exactly did you run the phpize and the generated configure? What are the autoconf, libtool and automake versions in your system? Checking configure generated on my machine, it's impossible for $host_alias to be empty unless you specify it to be empty with --host="" or someth

[PHP-DEV] PHP_SHLIB_SUFFIX not being properly set on MacOSX

2005-01-04 Thread Brad House
Just tried to phpize an extension, and it appears as though there is a problem on MacOSX. PHP_SHLIB_SUFFIX defaults to .so because a check is run on $host_alias, which is set to "". Attached is a patch to use $host_os instead which fixes the problem. This is against php-4.3.10 by the way. I have