I've tried to follow the suggestions in the other thread about this, but it
doesn't seem applicable. I have the following files set up on a Linux 2.6
64-bit box running PHP 5.3.2 (64-bit). The ARAPI is version 7.1 p1 for Linux
and the RTL version is the latest. I am using the latest PHP ARAPI source
files.
I wonder how the config.log file looks where it tries to verify that -lar is
working.
Another thought is that, is this really going to work, compile it as 64-bit
and linking a 32-bit library. And that maybe resulting in, can you compile
this as 32-bit and run it on a 64-bit apache/php server. I can not say for
sure. At the moment ARAPI only available as 64-bit in 7.6.x and later. And so
far it is not very stable.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good point about ARAPI being 32-bit here... I'm quite certain that PHP will
not be able to load a 32-bit library if it is 64-bit, at least not without
some additional magic not built in by default. I assumed that the ARAPI I had
also had 64-bit binaries, but I guess I assumed too much.
For what's it worth, here is the section of config.log you mentioned:
configure:4282:checkingforARInitializationin-larconfigure:4317:cc-oconftest-g-O2-Wl,-rpath,/root/php_arapi_build/arapi//lib -L/root/php_arapi_build/arapi//lib-pthread-ldlconftest.c-lar>&5/usr/bin/ld: skipping incompatible /root/php_arapi_build/arapi//lib/libar.sowhensearchingfor-lar/usr/bin/ld: skipping incompatible /root/php_arapi_build/arapi//lib/libar.awhensearchingfor-lar/usr/bin/ld:cannotfind-larcollect2:ldreturned1exitstatusconfigure:4324:$?=1configure:failedprogramwas:|/* confdefs.h. */|#definePACKAGE_NAME""|#definePACKAGE_TARNAME""|#definePACKAGE_VERSION""|#definePACKAGE_STRING""|#definePACKAGE_BUGREPORT""|/* end confdefs.h. */||/* Override any GCC internal prototype to avoid an error.| Use char because int might match the return type of a GCC| builtin and then its argument prototype would still apply. */|#ifdef__cplusplus|extern"C"|#endif|charARInitialization();|int|main()|{|returnARInitialization();|;|return0;|}configure:4345:result:noconfigure:4501:error:arapiisneeded
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've tried to follow the suggestions in the other thread about this, but it
doesn't seem applicable. I have the following files set up on a Linux 2.6
64-bit box running PHP 5.3.2 (64-bit). The ARAPI is version 7.1 p1 for Linux
and the RTL version is the latest. I am using the latest PHP ARAPI source
files.
This is the result of running configure:
Do you have /root/php_arapi_build/arapi/lib in LD_LIBRARY_PATH ??
I wonder how the config.log file looks where it tries to verify that -lar is
working.
Another thought is that, is this really going to work, compile it as 64-bit
and linking a 32-bit library. And that maybe resulting in, can you compile
this as 32-bit and run it on a 64-bit apache/php server. I can not say for
sure. At the moment ARAPI only available as 64-bit in 7.6.x and later. And so
far it is not very stable.
Good point about ARAPI being 32-bit here... I'm quite certain that PHP will
not be able to load a 32-bit library if it is 64-bit, at least not without
some additional magic not built in by default. I assumed that the ARAPI I had
also had 64-bit binaries, but I guess I assumed too much.
For what's it worth, here is the section of config.log you mentioned:
I guess that mean it finds files that match -lar but can not use them. And
this might be the 64/32 -bit problem.
OK, I really appreciate your quick replies on this! I'll look into running
32-bit Apache/PHP and try this again. Thanks.