1833341 Members
3898 Online
110051 Solutions
New Discussion

php compile

 
이현석_3
Occasional Contributor

php compile

Iplanet + php 4.3.7 + oracle client

State :
Iplanet, oracle client : installed
compiler : gcc

When php compile, I had a message,

#./configure --with-oci8=/orahome --with-nsapi=/iplanet/server

---------
cp: cannot access libs/libphp4.sl: No such file or directory
make: *** [install-sapi] Error 1
---------
After 'make' , In php/libs directory *.sl file is not in.

1. library path problem?
In .profile file,
LD_LIBRARY_PATH=/usr/lib:/usr/local/lib

or
2. ld problem?
when it is compiled, warning message display

----message
*** Warning: linker path does not have real file for library -l:libcl.a.
I have the capability to make that library automatically link in when you link to this library. But I can only do this if you have a
shared version of the library, which you do not appear to have because I did check the linker path looking for a file starting
with lib:libcl.a and none of the candidates passed a file format test
using a file magic. Last file checked: /lib/libnsl.1

Warning: linker path does not have real file for library -l:librt.sl.
I have the capability to make that library automatically link in when
you link to this library. But I can only do this if you have a shared version of the library, which you do not appear to have
because I did check the linker path looking for a file starting with lib:librt.sl and none of the candidates passed a file format test
using a file magic. Last file
checked: /lib/libnsl.1
------------

or
3. other message
/usr/ccs/bin/ld: (Warning) At least one PA2 object file (su9_prt.o) was detected. The linked output may not work on PA 1.x system.

Is there different between PA2.X and PA1.x?
(I don't know about hpux)

3 REPLIES 3
Steve Steel
Honored Contributor

Re: php compile

Hi

For 1 and 2 look at

LD_PRELOAD is implemented as part of dynamic
linker so that libraries specified in
LD_PRELOAD env variable are loaded as part
of a.out dependent's list.

Point 3 there are differences and thus the message

You should always try to compile on the platform you wish to use or use

For compatible code across both PA_RISC 1.1 and 2.0 workstations and
servers, use the +DAportable option.

Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
이현석_3
Occasional Contributor

Re: php compile

1. In .profile file,
I have to set, 'LD_PRELOAD=/usr/lib' ?

---
For compatible code across both PA_RISC 1.1 and 2.0 workstations and
servers, use the +DAportable option.
---

where is setting option, '+DAportable'?
^^;

이현석_3
Occasional Contributor

Re: php compile

I add warning messages,
I don't know that php/libs/*.sl file don't create

-------
*** Warning: linker path does not have real file for library -l:libdld.sl.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
with lib:libdld.sl and none of the candidates passed a file format test
using a file magic. Last file checked: /lib/libnsl.1

*** Warning: libtool could not satisfy all declared inter-library
dependencies of module libphp4. Therefore, libtool will create
a static module, that should work as long as the dlopening
application is linked with the -dlopen flag.
-------------