ID: 25810 Updated by: [EMAIL PROTECTED] Reported By: sbrennan at southerncountiestitle dot com -Status: Open +Status: Wont fix Bug Type: Feature/Change Request Operating System: RH 9 kernel 2.6.0-test6 PHP Version: 5.0.0b1 (beta1) New Comment:
I don't see how it's related to PHP at all. I'm doing a lot of work with PHP, but that doesn't mean PHP should have all configure options I can think of. Previous Comments: ------------------------------------------------------------------------ [2003-10-09 14:59:34] sbrennan at southerncountiestitle dot com I apologise for the above. I just read it and I thought English was my second language. Step 1: Compile DMALLOC for testing in a version specific path (ex. /usr/local/dmalloc.v.X) Step 2: Compile NET-SNMP with DMALLOC libs (./configure ...--with-dmalloc[=DIR] ... Step 3: Run configure in PHP5 source, and --with-snmp[=DIR]. (no --enable-dmalloc) running the configure script returns no errors, but a make kicks out with a "can't find dmalloc.h" error. Simple solution would be to give --with-dmalloc[=DIR] instead of --enable-dmalloc OR in the manual, (common sense, I know) remind everyone that if no path is allowed for a particular switch, then it must be in the search path of the makefile, or, if looking in a makefile is too much, directions to symbolicly link the necessary lib and include files to /usr/local/ or whatever. ------------------------------------------------------------------------ [2003-10-09 14:47:31] sbrennan at southerncountiestitle dot com Description: ------------ Simple run, without enabling dmalloc, if dmalloc is enabled in another program that is then compiled into php, php still requires the dmalloc libs and includes. I know this is obvious, but other apps allow admins to place the dmalloc in a particular place, especially if they are testing multiple installations, etc. Currently, php5 configure script does not allow for the explicit naming of a dmalloc path, etc. Not a bug, but can be confusing for others, if they did not ask for dmalloc, but it fails because snmp was able to explicitly name the path to dmalloc, and the user wants snmp functions. Its splitting hairs, but I figured I'd tell you, since someone reported it to me as a bug. I linked the correct version of dmalloc into the /usr/local directories, and it compiles fine. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=25810&edit=1
