Doc #41231 [Asn->Opn]: x86_64 config library path search documentation problem

Edit report at http://bugs.php.net/bug.php?id=41231&edit=1 ID: 41231 Updated by: kalle@php.net Reported by: hillct-php-bugreport at cthill dot org Summary: x86_64 config library path search documentation problem -Status: Assigned +Status: Open Type: Documentation Problem Package: Documentation problem Operating System: Lunux (fc4-fc6) x86_64 PHP Version: 5CVS-2007-04-29 (snap) -Assigned To: kalle +Assigned To: Block user comment: N New Comment: Unassigning myself, I have no idea why it was assigned to me. So a doc-linux guy should pick this up instead :) Previous Comments: ------------------------------------------------------------------------ [2008-01-11 22:49:56] o_orca at hotmail dot com I am getting this problem on RHEL 4 64-bit. I'm installing PHP-5.2.5 I have included --with-libdir=lib64 and --with-mysql=/usr/local/mysql I added the specific mysql dir because I've install MySQL from the tarball instead of taking what RedHat gave me. Full config command: ./configure --with-apxs2=/usr/local/apache2/bin/apxs --prefix=/usr/local/apache2/php --with-mysql=/usr/local/mysql --with-mysql-sock --with-mysqli=/usr/local/mysql/bin/mysql_config --disable-posix --enable-calendar --enable-memory-limit --with-libdir=lib64 --with-pear --with-gd --with-jpeg-dir --with-png-dir --with-zlib-dir --without-sqlite --without-pdo-sqlite --with-pdo-mysql --enable-sockets --sysconfdir=/etc --with-config-file-path=/etc This command without the pear and libdir parts is what I've been using on RHEL4 32-bit machines for some time. Never had a problem before trying it on this 64-bit system. Anyone have a good solution? Would appreciate the help. ------------------------------------------------------------------------ [2007-08-22 17:30:31] hillct-php-bugreport at cthill dot org The ./configure --help display is a bit vague but at least it doesn't say 'path to libdir' which is what I found somewhere else. It's been a while since I looked at this so I don't recall exactly. I grepped through the docs in the tarball and none of them seem to contain the problem wording. It could have been on php.net or some place more innocuous and not directly related to the project like one of the mailing lists. At any rate, it would be beneficial if the INSTALL document mentioned the proper formatting of the libdir argument. It's also possibly I simply misinterpreted the notation convention included with the ./configure --help results, but there seem to be plenty of others who have made the same error, so regardless of whether it's technically correct, it's probably worth clarifying or highlighting somewhere more prominent. When I get some more time, I'll look further into where I found the problematic documentation explicitly specifying full path. Clearly I should have taken better notes when initially submitting the bug. ------------------------------------------------------------------------ [2007-08-22 17:10:01] tularis@php.net "The documentation indicates that --with-libdir should be used to specify a full path" Could you please specify where you found that exactly? I can't seem to find any mention of the --with-libdir flag in the online documentation. ------------------------------------------------------------------------ [2007-04-30 13:03:37] sniper@php.net "experts" :D ------------------------------------------------------------------------ [2007-04-30 11:55:08] hillct-php-bugreport at cthill dot org The documentation indicates that --with-libdir should be used to specify a full path, which is a case tested before this bug was submitted. The documentation should be updated to reflect use of the libdir argument with relative paths or path fragments. Having consulted many supposed expert php developers, who have all told me the configure script is broken in this way (one having given me the patch as a solution), it seems the documentation needs to be clarified on this point. ------------------------------------------------------------------------ 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/bug.php?id=41231 -- Edit this bug report at http://bugs.php.net/bug.php?id=41231&edit=1