#32300 [Com]: 64bit libraries in */lib and */lib64
ID: 32300 Comment by: public at caffeianted dot org Reported By: axelseaa at amadmax dot com Status: No Feedback Bug Type: Compile Failure Operating System: Fedora Core 3 64 Bit PHP Version: 5.0.3 New Comment: Same problem here. On CentOS 4.5 manually installing Apache 1.3.31 and PHP 4.4.2 and when I try to add --with-ldap, it needs to have --with-ldap=/usr/lib64 specified but then it can't find the ldap.h file which is located in the /usr/lib directory. How can I make this work? Previous Comments: [2007-03-23 17:12:29] rwarner at snaplogic dot org The problem persists. I am having the same problem in 5.2.1 trying to configure on RedHat ES 4 x64_86. It still looks for the LDAP libraries in /usr/lib rather than /usr/lib64 even with the appropriate flag set to configure to tell it to use /usr/lib64 for the libraries. [2005-04-02 07:41:34] darren at cpanel dot net This also happens on RHEL 3. The vendor installs libraries via up2date/rpms to both /usr/lib/ and /usr/lib64/ , however the php configure script (4.3.11) has $i/lib/library.ext hardcoded in, where $i=/usr/ and the library.ext we need to link against was installed by the vendor in /usr/lib64/ . A couple examples are libjpeg and libpng, both put in /usr/lib64/ (needed with the common GD support). [2005-03-25 01:49:09] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to Open. Thank you. [2005-03-18 19:37:22] [EMAIL PROTECTED] *sigh* You can always tell in configure of those mysql and postgresql where they put the libraries.. IMO, you should always do whatever the distribution packages does: In this case: Put the 64bit libs in /lib64 !! [2005-03-16 15:26:22] axelseaa at amadmax dot com Jabber compiles get around this by offering the following configuration option: --with-extra-library-path=/usr/lib:/usr/lib64:/some/other/lib Would something like this be doable? 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/32300 -- Edit this bug report at http://bugs.php.net/?id=32300edit=1
#32300 [Com]: 64bit libraries in */lib and */lib64
ID: 32300 Comment by: rwarner at snaplogic dot org Reported By: axelseaa at amadmax dot com Status: No Feedback Bug Type: Compile Failure Operating System: Fedora Core 3 64 Bit PHP Version: 5.0.3 New Comment: The problem persists. I am having the same problem in 5.2.1 trying to configure on RedHat ES 4 x64_86. It still looks for the LDAP libraries in /usr/lib rather than /usr/lib64 even with the appropriate flag set to configure to tell it to use /usr/lib64 for the libraries. Previous Comments: [2005-04-02 07:41:34] darren at cpanel dot net This also happens on RHEL 3. The vendor installs libraries via up2date/rpms to both /usr/lib/ and /usr/lib64/ , however the php configure script (4.3.11) has $i/lib/library.ext hardcoded in, where $i=/usr/ and the library.ext we need to link against was installed by the vendor in /usr/lib64/ . A couple examples are libjpeg and libpng, both put in /usr/lib64/ (needed with the common GD support). [2005-03-25 01:49:09] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to Open. Thank you. [2005-03-18 19:37:22] [EMAIL PROTECTED] *sigh* You can always tell in configure of those mysql and postgresql where they put the libraries.. IMO, you should always do whatever the distribution packages does: In this case: Put the 64bit libs in /lib64 !! [2005-03-16 15:26:22] axelseaa at amadmax dot com Jabber compiles get around this by offering the following configuration option: --with-extra-library-path=/usr/lib:/usr/lib64:/some/other/lib Would something like this be doable? [2005-03-16 13:51:53] axelseaa at amadmax dot com They are both build for 64 bit system, its just that the fedora build rpms stick the libs in the lib64 folder, where the custom compiled ones do not. 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/32300 -- Edit this bug report at http://bugs.php.net/?id=32300edit=1
#32300 [Com]: 64bit libraries in */lib and */lib64
ID: 32300 Comment by: darren at cpanel dot net Reported By: axelseaa at amadmax dot com Status: No Feedback Bug Type: Compile Failure Operating System: Fedora Core 3 64 Bit PHP Version: 5.0.3 New Comment: This also happens on RHEL 3. The vendor installs libraries via up2date/rpms to both /usr/lib/ and /usr/lib64/ , however the php configure script (4.3.11) has $i/lib/library.ext hardcoded in, where $i=/usr/ and the library.ext we need to link against was installed by the vendor in /usr/lib64/ . A couple examples are libjpeg and libpng, both put in /usr/lib64/ (needed with the common GD support). Previous Comments: [2005-03-25 01:49:09] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to Open. Thank you. [2005-03-18 19:37:22] [EMAIL PROTECTED] *sigh* You can always tell in configure of those mysql and postgresql where they put the libraries.. IMO, you should always do whatever the distribution packages does: In this case: Put the 64bit libs in /lib64 !! [2005-03-16 15:26:22] axelseaa at amadmax dot com Jabber compiles get around this by offering the following configuration option: --with-extra-library-path=/usr/lib:/usr/lib64:/some/other/lib Would something like this be doable? [2005-03-16 13:51:53] axelseaa at amadmax dot com They are both build for 64 bit system, its just that the fedora build rpms stick the libs in the lib64 folder, where the custom compiled ones do not. [2005-03-16 07:49:33] [EMAIL PROTECTED] You should not mix 32bit libs with 64bit ones, iirc.. 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/32300 -- Edit this bug report at http://bugs.php.net/?id=32300edit=1
