Re: Why zend_language_scanner_cc.cc instead of zend_language_scanner.c?

From: Date: Wed, 20 Dec 2000 17:46:48 +0000
Subject: Re: Why zend_language_scanner_cc.cc instead of zend_language_scanner.c?
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-41965@lists.php.net to get a copy of this message
--with-servlet probably enables zts automatically and the thread-safe build breaks on your system. It is supposed to compile the .cc file instead of the .c file. Andi At 12:40 20/12/00 -0500, Bill Stoddard wrote:
I am configuring thusly... export CCxlc_r export CFLAGS="-ma -g" ./configure --without-xml --without-mysql --with-java=/usr/jdk_base --with-ser vlet=/path/to/servlet.jar So I am not explicitly using --with-experimental-zts. I see the segfault when attempting to run date.php (or any other php script) under TomCat 3.2.1. Should've mentioned that in my first post. Bill ----- Original Message ----- From: Andi Gutmans <andi@zend.com> To: Bill Stoddard <bill@wstoddard.com>; <php-dev@lists.php.net> Sent: Wednesday, December 20, 2000 12:16 PM Subject: Re: [PHP-DEV] Why zend_language_scanner_cc.cc instead of zend_language_scanner.c? You shouldn't be using --with-experimental-zts unless you're compiling for a multi-threaded web server. Andi At 12:17 20/12/00 -0500, Bill Stoddard wrote:
Trying to debug a SEGFAULT on AIX and I think it is related to the fact
that
my configuration is compiling zend_language_scanner_cc.cc rather than zend_language_scanner.c. How can I make zend_language_scanner.c be
compiled
instead of zend_language_scanner_cc.cc? I think you can safely ignore the 'warning' messages. Thanks, Bill
bash-2.04$ make /bin/sh ../libtool --silent --mode=compile
c++ -DHAVE_CONFIG_H -I. -I. -I../main -D_THREAD_SAFE -I../TSRM -g
-O2 -c
zend_language_scanner_cc.cc
In file included from ../TSRM/TSRM.h:32,
                 from zend_alloc.h:27,
                 from zend.h:133,
                 from zend_language_scanner_cc.cc:2662:
/usr/include/pthread.h:113: warning: missing white space after `#define
PTHREAD_MUTEX_INITIALIZER'
/usr/include/pthread.h:128: warning: missing white space after `#define
PTHREAD_COND_INITIALIZER'
/usr/include/pthread.h:147: warning: missing white space after `#define
PTHREAD_RWLOCK_INITIALIZER'
/usr/include/pthread.h:157: warning: missing white space after `#define
PTHREAD_ONCE_INIT'
/bin/sh ../libtool --silent --mode=compile
c++ -DHAVE_CONFIG_H -I. -I. -I../main -D_THREAD_SAFE -I../TSRM -g
-O2 -c
zend_ini_scanner_cc.cc
In file included from ../TSRM/TSRM.h:32,
                 from zend_alloc.h:27,
                 from zend.h:133,
                 from zend_ini_scanner_cc.cc:403:
/usr/include/pthread.h:113: warning: missing white space after `#define
PTHREAD_MUTEX_INITIALIZER'
/usr/include/pthread.h:128: warning: missing white space after `#define
PTHREAD_COND_INITIALIZER'
/usr/include/pthread.h:147: warning: missing white space after `#define
PTHREAD_RWLOCK_INITIALIZER'
/usr/include/pthread.h:157: warning: missing white space after `#define
PTHREAD_ONCE_INIT'
/bin/sh ../libtool --silent --mode=link c++ -g -O2 -o libZend_cc.la
zend_language_scanner_cc.lo zend_ini_scanner_cc.lo
/bin/sh ../libtool --silent --mode=compile
xlc_r -DHAVE_CONFIG_H -I. -I. -I../main -D_THREAD_SAFE -I../TSRM -ma -g -c
zend_language_parser.c
/bin/sh ../libtool --silent --mode=compile
xlc_r -DHAVE_CONFIG_H -I. -I. -I../main -D_THREAD_SAFE -I../TSRM -ma -g -c
zend_ini_parser.c
/bin/sh ../libtool --silent --mode=compile
xlc_r -DHAVE_CONFIG_H -I. -I. -I../main -D_THREAD_SAFE -I../TSRM -ma -g -c
zend_alloc.c <snip> -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net
--- Andi Gutmans <andi@zend.com> http://www.zend.com/
--- Andi Gutmans <andi@zend.com> http://www.zend.com/

« previous php.dev (#41965) next »