ID:               19918
 User updated by:  [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Open
-Bug Type:         Apache2 related
+Bug Type:         *Compile Issues
 Operating System: HP-UX 11.00
-PHP Version:      4.3.0-pre1
+PHP Version:      4.3.0
 New Comment:

Changed category from Apache2 to Compile Issues

I've tested now with apache 1.3.x and the result is the same. What is
the other bug saying that is doesn't work with apache 1.3.x ?

Now (with 4.3.0) the error when we make install is : 

Installing PHP CLI binary:        /PKl01h01/soft/web/bin/
Installing PHP SAPI module
apxs:Error: file libs/libphp4.sl is not a DSO
*** Error exit code 1

Stop.
-----------------------------
There's no libs/libphp4.sl


php 4.2.3 libs produce (OK) : 

libphp4.la
libphp4.sl

php 4.3.0 libs produce (not OK) : 

libphp4.a
libphp4.la

What can I do ? Do you have reproduced the suggestion 
of [EMAIL PROTECTED] with -lcrypt ?

@++
JC


Previous Comments:
------------------------------------------------------------------------

[2002-12-23 04:57:43] [EMAIL PROTECTED]

Same result with PHP 4.3.0RC4

It's a critical bug in "Apache2 related" category.
Can you change the status to critical ?

@++
JC

------------------------------------------------------------------------

[2002-12-11 12:04:11] [EMAIL PROTECTED]

tested with php4-200212111630

same result.

@++
JC

------------------------------------------------------------------------

[2002-11-26 18:46:28] [EMAIL PROTECTED]

Using the latest CVS snapshot php4-STABLE-200211262230, I was able to
locate what I believe to be the problem.  Apparently PHP is trying to
link in -lcrypt, and because libcrypt.a is not a shared library object,
libtool is complaining and then not creating a shared libphp.so object
because of it:

*** Warning: linker path does not have real file for library -lcrypt.
*** 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 libcrypt and none of the candidates passed a file format test
*** using a file magic. Last file checked: /usr/lib/libcrypt.a

*** 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.

So what I did was re-run the last libtool command, which is supposed to
link all the objects together, and create a libphp4.so, but I took out
the -lcrypt portion of the command. Once that was done, a libphp4.so
was created as expected, and then a 'make install' worked also as
expected putting libphp4.so into /opt/apache/modules.  Starting apache
so far also works without an error about 'Bad magic number'.  I took a
gamble that php didn't use or require the crypt library, otherwise I
was half expecting to get an error from dld.sl about missing reference
to 'crypt', but so far so good.

------------------------------------------------------------------------

[2002-11-21 14:27:38] [EMAIL PROTECTED]

tested with php4-200211211830

same result.

@++
JC

------------------------------------------------------------------------

[2002-11-19 18:59:57] [EMAIL PROTECTED]

I'm having the same problem and I'm using the latest CVS snapshot of
php4-200211200030, HP-UX 11.00 and Apache 2.0.43.

The only way I was able to work around the problem was to go into where
I have apache/modules located and rename libphp4.a to libphp4.so and
then 'make install' again.  This seems to work, but when I try to start
apache, it can't use the libphp4.so.  I get this error message:

Cannot load /opt/apache/modules/libphp4.so into server: Bad magic
number for shared library: /opt/apache/modules/libphp4.so

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/19918

-- 
Edit this bug report at http://bugs.php.net/?id=19918&edit=1

Reply via email to