ID: 22595
Updated by: [EMAIL PROTECTED]
Reported By: web at affenkrieger dot de
-Status: Verified
+Status: Bogus
Bug Type: Sybase-ct (ctlib) related
Operating System: Mandrake Linux 9.0
PHP Version: 4.3.2-dev
New Comment:
As mentioned in previous comment, this is Sybase's problem,
not PHP or Mandrake..
Previous Comments:
------------------------------------------------------------------------
[2003-03-23 13:14:10] jmdault at mandrakesoft dot com
I checked and Mandrake can't put libintl.so.2 elsewhere than /lib,
since it's needed by the initscripts, and it needs to be run before
/usr is mounted.
I guess you could simply do a rpm -e gettext-devel and it will compile
properly.
But the real issue is with Sybase, and all other software whose authors
lack imagination and use the same function names or library names as
other projects.
Jean-Michel
------------------------------------------------------------------------
[2003-03-10 10:45:49] [EMAIL PROTECTED]
Does not affect normal (static) build at all.
------------------------------------------------------------------------
[2003-03-10 04:29:10] web at affenkrieger dot de
Ok, i tried the new version of PHP -> didn't work.
So i made a dirty hack:
deleting all references to the "wrong" libintl.so in /lib and /usr/lib,
then recompiling PHP. voila, it works.
Since compiling DBD::Sybase worked perfectly, it has to be a problem
with the compilation routine of PHP. the lib path in
--with-sybase-ct=/path/to/sybase should be more important than other
(standard) lib paths. It seems that the compilation routine not even
respects settings like LD_LIBRARY_PATH
------------------------------------------------------------------------
[2003-03-08 11:46:31] web at affenkrieger dot de
Nope, neither /lib nor /usr/lib. Only additional lib paths like
$SYBASE/lib
------------------------------------------------------------------------
[2003-03-08 11:42:31] [EMAIL PROTECTED]
Do you have /lib in /etc/ld.so.conf ?
------------------------------------------------------------------------
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/22595
--
Edit this bug report at http://bugs.php.net/?id=22595&edit=1
