ID: 22109 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: DBM/DBA related Operating System: Solaris 2.7 PHP Version: 4CVS-2003-02-07 (stable) New Comment:
The system is a 32 bit Sun Ultra 1 168 MHz Sparc workstation loaded with 32 bit Solaris 7, 256MB memory, and 2 internal 2GB SCSI disks. All development software loaded on machine such as compilers and configuration ( autoconf stuff ) came either from the Sunfreeware site as a package or as a tarballs from GNU's site. Would appreciate the re-org'g of the configure messages. Note I have other questions regarding configure option usage and would like to know how or to whom I should submit them. Previous Comments: ------------------------------------------------------------------------ [2003-02-10 13:54:30] [EMAIL PROTECTED] Just another question what is your system: 32 or 64bit? To dba switches: You can see that information by either the function "dba_handlers()" or "php -i" or the output of the function "phpinfo()" (the last one creates layoted html output if called from your internet browser). And --with-dbXXX or other related dba switch turns DBA extension on. If you add --enable-dba then all default submodules which do not require external libraries are used, too (flatfile, cdb, cdb_make). Hope this helps. Maybe i reorganize the configure messages so that they do not confuse in the way you described it. regards marcus ------------------------------------------------------------------------ [2003-02-10 13:04:58] [EMAIL PROTECTED] Closed per user-request. (and seems like fixed too..?) ------------------------------------------------------------------------ [2003-02-10 12:54:15] [EMAIL PROTECTED] I downloaded a late Sunday evening snapshot and did not receive any of the mentioned core dumps as in previous posts. I've also reviewed the information provided at http://www.php.net/manual/en/ref.dba.php and learned that the flatfile interface is deprecated. Based on this, there seems no need to persist with this as a bug report. Go ahead and close it. ------------------------------------------------------------------------ [2003-02-07 20:03:35] [EMAIL PROTECTED] Here is the ldd output you asked for: libcrypt_i.so.1 => /usr/lib/libcrypt_i.so.1 libresolv.so.2 => /usr/lib/libresolv.so.2 libm.so.1 => /usr/lib/libm.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libpthread.so.1 => /usr/lib/libpthread.so.1 libc.so.1 => /usr/lib/libc.so.1 libgen.so.1 => /usr/lib/libgen.so.1 libmp.so.2 => /usr/lib/libmp.so.2 libthread.so.1 => /usr/lib/libthread.so.1 /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1 I tried to run your print_r( dba_handlers() ) but I got an undefined function error. That only shows up in the code with the --enable-dba option, an option not used in my configure script. I included it, then re-configured and did a full re-compile. Still had the core dump afterwards. The output from the print_r command is: Array ( [flatfile] => 1.0, $Revision: 1.5.2.3 $ ) ) Side question: is there a configure reference or rule that states if one option is present, these other options should be as well. As in the above, is the enable-dba option required in the presence of the --with-dbXX or --with-flatfile options. Without the --enable-dba present, I saw the message "checking whether DBA interface is enabled=yes" in the config output. This led me to believe that DBA was enabled. That was not the case based on your email and the subsequent config output "checking whether DBA is enabled=yes" showed up right before the earlier mentioned one. I'm new to PHP so this seems ambiguous to me! ------------------------------------------------------------------------ [2003-02-07 14:03:25] [EMAIL PROTECTED] Could you please send the outputs of "ldd php" and if you used shared builds then the ldd output of any loaded php module, too. And then i'd like to see the ouput of "php -r 'print_r(dba_handlers(1));'" if you did not use a cvs version then you must omit the parameter "1". ------------------------------------------------------------------------ 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/22109 -- Edit this bug report at http://bugs.php.net/?id=22109&edit=1
