Re: [Php-java-bridge-users] OSX Compile Issue

[Poorly <po...@ma...>]

Hi Jost,

OK, I compiled the bridge (with the extern patch) in with PHP (5.0.3) 
successfully as per the windows method but when starting apache I get 
the following in the error_log, which is part of the same error I had 
with the extension version :-
PHP Fatal error:  Cannot override final method java::?B?() in Unknown on 
line 0
PHP Fatal error:  Cannot override final method java::?B?() in Unknown on 
line 0
PHP Fatal error:  Cannot override final method java_exception::?B?() in 
Unknown on line 0

PHP Info Java section says :-
java support Enabled
 java bridge 1.0.8
 java command JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home 
LD_LIBRARY_PATH=/usr/local/lib/php/extensions/no-debug-non-zts-20041030 
/System/Library/Frameworks/JavaVM.framework/Home/bin/java 
-Djava.library.path=/usr/local/lib/php/extensions/no-debug-non-zts-20041030 
-Djava.class.path=/usr/local/lib/php/extensions/no-debug-non-zts-20041030 
-Djava.awt.headless=true JavaBridge /var/tmp//.php_java_bridgehkq3uI 0 ''
 java.libpath /usr/local/lib/php/extensions/no-debug-non-zts-20041030
 java.classpath /usr/local/lib/php/extensions/no-debug-non-zts-20041030
 java.java_home /System/Library/Frameworks/JavaVM.framework/Home
 java.java /System/Library/Frameworks/JavaVM.framework/Home/bin/java
 java.log_file <stdout>
 java.log_level 0
 java status not running

And when I go to a test page I get :-
Fatal error: php_mod_java(52): Could not connect to server: Socket 
operation on non-socket -- Have you started the java bridge? in 
/Library/WebServer/Documents/phpjava.php on line 2

I've also tried hacking the Makefiles to add in -flat_namespaces and 
-export-dynamic but still no luck.

CHEERS
Paul

> Jost,
>
>>[please excuse the delay]
>>
>>  
>>
> No problem, I appreciate the help.
>
>>  
>>
>>>-ZEND_DECLARE_MODULE_GLOBALS(java)
>>>+extern ZEND_DECLARE_MODULE_GLOBALS(java)
>>>    
>>>
>>
>>Thanks.  I will commit this shortly.
>>
>>
>>  
>>
>>>-libtoolize -f
>>>+glibtoolize -f
>>>    
>>>
>>
>>
>>We need the gnu autoconf/automake/libtool anyway as the apple versions
>>(at least the installation at SF) don't work properly.  So I think the
>>change is not necessary.
>>
>>
>>  
>>
>>>java.lang.UnsatisfiedLinkError: no natcJavaBridge in java.library.path
>>>        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1517)
>>>        at java.lang.Runtime.loadLibrary0(Runtime.java:788)
>>>        at java.lang.System.loadLibrary(System.java:834)
>>>        at JavaBridge.main(JavaBridge.java:520)
>>>    
>>>
>>
>>Which java version have you used?  BTW: Are there other java
>>implementations than the one from apple?  The apple JIT crashes after
>>running the bridge for one hour.  I don't think it's a problem with the
>>bridge but rather a bug in the JIT; running a pure java version of the
>>scheme-demo has the same effect.
>>
>>  
>>
> As far as I know apples implementation is the only one. Mind you 
> /System/Library/Frameworks/JavaVM.framework/Versions/ indicates we can 
> use 1.2, 1.3, 1.3.1, and 1.4.2 with 1.4.2 being the default, would it 
> be worth trying a different version ?
>
>>  
>>
>>>dyld: /usr/sbin/httpd Undefined symbol
>>>_php_info_print_table_end
>>>    
>>>
>>
>>No idea what this is (I haven't tested apache, yet).  But it sounds as
>>if the dynamic loader cannot re-export symbols from a dynamic library:
>>apache dlopen()s PHP which in turn must dlopen() the bridge in such a
>>way that the PHP symbols are exported to the bridge.  
>>  
>>
> apples dynamic loader weirdness :-). I'll google a bit on the 
> "re-export" clue ...
>
>>The fact that the httpd complains about missing symbols rather than PHP
>>doesn't sound good, maybe it's an issue with PHP not invoking dlopen()
>>correctly on this system. It might be necessary to compile the bridge
>>directly into PHP; please see the windows install instructions for
>>details.
>>
>>
>>  
>>
> I'll have a go at that too.
>
> Also I'm running an up to date Panther (10.3.7) build, but I am 
> running a home brew php-5.0.3 so I'll also try reverting to the 
> default php-4.3.? and see if it works there.
>
>>Jost
>>
>>
>>  
>>
>
> CHEERS
> Paul