ID: 22796 Comment by: 98181011 at 263 dot sina dot com Reported By: gk at proliberty dot com Status: No Feedback Bug Type: CGI related Operating System: linux RH 7.2 PHP Version: 4CVS-2003-03-19 (stable) New Comment:
i've tryed using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz and come with the following error: /usr/local/lib/libsablot.so: undefined reference to `operator new[](unsigned)' /usr/local/lib/libsablot.so: undefined reference to `vtable for __cxxabiv1::__si_class_type_info' /usr/local/lib/libsablot.so: undefined reference to `operator delete(void*)' /usr/local/lib/libsablot.so: undefined reference to `__gxx_personality_v0' /usr/local/lib/libsablot.so: undefined reference to `__cxa_pure_virtual' /usr/local/lib/libsablot.so: undefined reference to `vtable for __cxxabiv1::__class_type_info' /usr/local/lib/libsablot.so: undefined reference to `operator delete[](void*)' /usr/local/lib/libsablot.so: undefined reference to `vtable for __cxxabiv1::__vmi_class_type_info' /usr/local/lib/libsablot.so: undefined reference to `operator new(unsigned)' collect2: ld returned 1 exit status make: *** [sapi/cli/php] Error 1 i don't know how to solve it,although i have spent a lot time would you please tell me how can i do? Previous Comments: ------------------------------------------------------------------------ [2003-03-31 01:56:57] [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. ..and can not reproduce.. ------------------------------------------------------------------------ [2003-03-24 17:43:41] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip I absolutely cannot replicate the problem you've described using the latest sources. ------------------------------------------------------------------------ [2003-03-24 16:59:21] gk at proliberty dot com OK. Now this is starting to make some sense, thanks to michael's last comment: >The message starting with "Fatal error:" goes to stdout, the other two to stderr. The whole issue here now is php.ini config. It is confusing in this particular example since there are THREE different errors for the same code input, two generated at startup, one later; two go to /dev/stderr, one to /dev/stdout. The issue is further complicated with the precedence of -c and -d options on the command line I think, but that will be discussed elsewhere.... [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -c $(pwd)/php.ini-recommended -r 'f();' PHP Fatal error: Call to undefined function: f() in Command line code on line 1 The above error is generated with .ini file settings: display_startup_errors = Off display_errors = Off log_errors = On ;error_log = filename So the error_log file must default to /dev/stderr Hence, this bug should be CLOSED now since the error IS displayed, if log_erros = On. The other error messages below appear to be startup errors, require display_startup_errors=On [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -c $(pwd)/php.ini-dist -r 'f();' [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -c $(pwd)/php.ini-dist -i|grep php.ini Configuration File (php.ini) Path => /usr/local/src/php4-STABLE-200303241830/php.ini-dist [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=On -r 'f();' [24-Mar-2003 14:34:21] PHP Fatal error: Call to undefined function: f() in Command line code on line 1 [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=On -r 'f();' 2>/dev/null [EMAIL PROTECTED] php4-STABLE-200303241830]# sapi/cli/php -d log_errors=1 -d error_log=/dev/stderr -d display_startup_errors=1 -r 'f();' 2>/dev/null Fatal error: Call to undefined function: f() in Command line code on line 1 [EMAIL PROTECTED] php4-STABLE-200303241830]# ------------------------------------------------------------------------ [2003-03-24 10:37:37] michael dot mauch at gmx dot de With php4-STABLE-200303241430 (and with 4.3.1), I can get even three error messages for the same error. # sapi/cli/php -c php.ini-dist -r 'f();' Command line code(1) : Fatal error - Call to undefined function: f() # sapi/cli/php -c php.ini-recommended -r 'f();' PHP Fatal error: Call to undefined function: f() in Command line code on line 1 Command line code(1) : Fatal error - Call to undefined function: f() # sed 's/\(display_.*errors = \)Off/\1On/' <php.ini-recommended >php.ini-display-errors # sapi/cli/php -c php.ini-display-errors -r 'f();' PHP Fatal error: Call to undefined function: f() in Command line code on line 1 Command line code(1) : Fatal error - Call to undefined function: f() Fatal error: Call to undefined function: f() in Command line code on line 1 This last php.ini is with display_errors and display_startup_errors = On. The message starting with "Fatal error:" goes to stdout, the other two to stderr. ------------------------------------------------------------------------ [2003-03-24 04:12:26] [EMAIL PROTECTED] And get first the latest stable snapshot again. ------------------------------------------------------------------------ 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/22796 -- Edit this bug report at http://bugs.php.net/?id=22796&edit=1
