Hi!
Is it expected that compiling as 32-bit on 64-bit will succeed?
I'm seeing "EXTRA_CFLAGS=-m32 make" bomb
in ext/opcache/zend_accelerator_util_funcs.c.
One problem I notice is that one definition of accel_xlat_get() takes one
argument, another takes two. (Source.
https://github.com/php/php-src/blob/master/ext/opcache/zend_accelerator_util_funcs.c#L31)
Only the one argument version is used. (Source.
https://github.com/php/php-src/blob/master/ext/opcache/zend_accelerator_util_funcs.c#L160)
The two argument version is never used. (And that second argument is
passed as the fourth formal argument and the return value
of zend_hash_str_find_ptr, which only takes 3 arguments and returns void.)
There are other problems though. Before I go down this path, I wanted to
check if -m32 was meant to be used.
Thanks,
bishop
I use 'CC="gcc -m32" ./configure' to build 32-bit PHP on 64-bit Linux.
This works fine, if you have all necessary 32-bit libraries and dev
packages.
Thanks. Dmitry.
Hi!
Is it expected that compiling as 32-bit on 64-bit will succeed?
I'm seeing "EXTRA_CFLAGS=-m32 make" bomb
in ext/opcache/zend_accelerator_util_funcs.c.One problem I notice is that one definition of accel_xlat_get() takes one
argument, another takes two. (Source.
<
https://github.com/php/php-src/blob/master/ext/opcache/zend_accelerator_util_funcs.c#L31)
Only the one argument version is used. (Source.
<
https://github.com/php/php-src/blob/master/ext/opcache/zend_accelerator_util_funcs.c#L160
)
The two argument version is never used. (And that second argument is
passed as the fourth formal argument and the return value
of zend_hash_str_find_ptr, which only takes 3 arguments and returns void.)There are other problems though. Before I go down this path, I wanted to
check if -m32 was meant to be used.Thanks,
bishop