Hello all,
System:
FreeBSD 7.0-PRERELEASE i386 Wed Jan 16 18:39:53 PST 2008
Context:
After several failed attempts to get a /stable/ installation of Apache13-ssl
and friends built and installed from source (see thread:
/usr/bin/objformat, for
more background). I chose to look at the possibility of using Apache
2.0. I was
reluctant, as doing so would require migrating ~50 carefully crafted
conf files
which have evolved over many yrs. to be now seemingly impervious to abuse, or
attack. I hadn't intended this server to become a guinea pig, but my ill
fated
attempts to install a stable copy of www/apache13-ssl from source necessitated
increasing the resources on the other servers. So as to experiment on
this one.
To the point!
Building Apache 2.0 on this box requied cvsupping src/ports (2008-01-30).
As the version of Apache 2.0 was 2.0.61 (has 2 security related issues).
Current version:
2.0.63. Building/installing this version went w/o trouble. Ran as expected.
I only made 1 mod from the default config/build: WITH_MPM?= threadpool.
The original was: WITH_MPM?= prefork. My diong so also required: KQUEUE.
Other than that, all was as-was.
Error(s):
After determining that everything was acceptablr/as intended with Apache.
I moved on to building/installing php5 as cgi,cli, and module. The first
thing emitted when typing make is:
[: -le: argument expected
[: -le: argument expected
This gets emitted once more early in the configure process. Followed by:
configure.in:152: warning: AC_PROG_LEX invoked multiple times
../../lib/autoconf/programs.m4:779: AC_DECL_YYTEXT is expanded from...
aclocal.m4:2080: PHP_PROG_LEX is expanded from...
configure.in:152: the top level
The build finally /dies/ with the following otput (with context):
...
Thank you for using PHP.
config.status: creating php5.spec
config.status: creating main/build-defs.h
config.status: creating scripts/phpize
config.status: creating scripts/man1/phpize.1
config.status: creating scripts/php-config
config.status: creating scripts/man1/php-config.1
config.status: creating sapi/cli/php.1
config.status: creating main/php_config.h
config.status: executing default commands
===> Building for php5-5.2.5_1
"Makefile", line 592: warning: duplicate script for target
"main/internal_functions.lo" ignored
...
-I/usr/ports/lang/php5/work/php-5.2.5/Zend -O2 -fno-strict-aliasing
-pipe -prefer-non-pic -c
/usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c -o
sapi/apache/sapi_apache.lo
/usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c: In
function 'apache_php_module_main':
/usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c:44:
error: 'NOT_FOUND' undeclared (first use in this function)
/usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c:44:
error: (Each undeclared identifier is reported only once
/usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c:44:
error: for each function it appears in.)
*** Error code 1
Stop in /usr/ports/lang/php5/work/php-5.2.5.
*** Error code 1
Stop in /usr/ports/lang/php5.
*** Error code 1
From sapi_apache.c:
if (display_source_mode) {
zend_syntax_highlighter_ini syntax_highlighter_ini;
php_get_highlight_struct(&syntax_highlighter_ini);
if (highlight_file(SG(request_info).path_translated,
&syntax_highlighter_ini TSRMLS_CC) != SUCCESS) {
*** OFFENDING LINE (44) retval = NOT_FOUND;
}
} else {
Any chance somebody knows what is required to resolve this - pretty please?
Thank you for all your time and consideration.
--Chris H
--
panic: kernel trap (ignored)
> After several failed attempts to get a /stable/ installation of Apache13-ssl > and friends built and installed from source (see thread: /usr/bin/objformat, > for more background). I chose to look at the possibility of using Apache 2.0.Out of interest, why did you choose 2.0 and not 2.2 ? When I migrated away from 1.3 I originally tried 2.0 and had quite a bad time of it as I recall. So I left it a while and ended up going directly to 2.2, which has behaved beautifully. I can't solve your problem, but I can say that personal experience was 2.2 being easier to move to. -pete.
Quoting "Chris H." <chris#@1command.com>:> Hello all, > System: > FreeBSD 7.0-PRERELEASE i386 Wed Jan 16 18:39:53 PST 2008 > > Context: > After several failed attempts to get a /stable/ installation of Apache13-ssl > and friends built and installed from source (see thread: > /usr/bin/objformat, for > more background). I chose to look at the possibility of using Apache > 2.0. I was > reluctant, as doing so would require migrating ~50 carefully crafted > conf files > which have evolved over many yrs. to be now seemingly impervious to abuse, or > attack. I hadn't intended this server to become a guinea pig, but my > ill fated > attempts to install a stable copy of www/apache13-ssl from source > necessitated > increasing the resources on the other servers. So as to experiment on > this one. > > To the point! > Building Apache 2.0 on this box requied cvsupping src/ports (2008-01-30). > As the version of Apache 2.0 was 2.0.61 (has 2 security related issues). > Current version: > 2.0.63. Building/installing this version went w/o trouble. Ran as expected. > I only made 1 mod from the default config/build: WITH_MPM?= threadpool. > The original was: WITH_MPM?= prefork. My diong so also required: KQUEUE. > Other than that, all was as-was. > > Error(s): > After determining that everything was acceptablr/as intended with Apache. > I moved on to building/installing php5 as cgi,cli, and module. The first > thing emitted when typing make is: > [: -le: argument expected > [: -le: argument expected > > This gets emitted once more early in the configure process. Followed by: > > configure.in:152: warning: AC_PROG_LEX invoked multiple times > ../../lib/autoconf/programs.m4:779: AC_DECL_YYTEXT is expanded from... > aclocal.m4:2080: PHP_PROG_LEX is expanded from... > configure.in:152: the top level > > The build finally /dies/ with the following otput (with context): > ... > Thank you for using PHP. > > config.status: creating php5.spec > config.status: creating main/build-defs.h > config.status: creating scripts/phpize > config.status: creating scripts/man1/phpize.1 > config.status: creating scripts/php-config > config.status: creating scripts/man1/php-config.1 > config.status: creating sapi/cli/php.1 > config.status: creating main/php_config.h > config.status: executing default commands > ===> Building for php5-5.2.5_1 > "Makefile", line 592: warning: duplicate script for target > "main/internal_functions.lo" ignored > > ... > > -I/usr/ports/lang/php5/work/php-5.2.5/Zend -O2 > -fno-strict-aliasing -pipe -prefer-non-pic -c > /usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c -o > sapi/apache/sapi_apache.lo > /usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c: In > function 'apache_php_module_main': > /usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c:44: > error: 'NOT_FOUND' undeclared (first use in this function) > /usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c:44: > error: (Each undeclared identifier is reported only once > /usr/ports/lang/php5/work/php-5.2.5/sapi/apache/sapi_apache.c:44: > error: for each function it appears in.) > *** Error code 1 > > Stop in /usr/ports/lang/php5/work/php-5.2.5. > *** Error code 1 > > Stop in /usr/ports/lang/php5. > *** Error code 1 > > From sapi_apache.c: > if (display_source_mode) { > zend_syntax_highlighter_ini syntax_highlighter_ini; > > php_get_highlight_struct(&syntax_highlighter_ini); > if (highlight_file(SG(request_info).path_translated, > &syntax_highlighter_ini TSRMLS_CC) != SUCCESS) { > > *** OFFENDING LINE (44) retval = NOT_FOUND; > > } > } else { > > > Any chance somebody knows what is required to resolve this - pretty please? > > Thank you for all your time and consideration. > > --Chris HJust making the title more meaningful. The original wasn't very representitive of the problem. Sorry. --Chris> > > -- > panic: kernel trap (ignored) > > > > _______________________________________________ > freebsd-apache@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-apache > To unsubscribe, send any mail to "freebsd-apache-unsubscribe@freebsd.org" >-- panic: kernel trap (ignored)
Hello, and thank you for your reply. Quoting Lawrence Stewart <lstewart@freebsd.org>:> > Hi Chris, > > Firstly, a disclaimer: I'm not an expert so I might be behind the > times on what I'm about to tell you...Note taken. :)> > Chris H. wrote: > > Hello all, > > System: > > FreeBSD 7.0-PRERELEASE i386 Wed Jan 16 18:39:53 PST 2008 > > > > Context: > > After several failed attempts to get a /stable/ installation of > > Apache13-ssl > > and friends built and installed from source (see thread: > > /usr/bin/objformat, for > > more background). I chose to look at the possibility of using Apache > > 2.0. I was > > reluctant, as doing so would require migrating ~50 carefully crafted > > conf files > > which have evolved over many yrs. to be now seemingly impervious to > > abuse, or > > attack. I hadn't intended this server to become a guinea pig, but my ill > > fated > > attempts to install a stable copy of www/apache13-ssl from source > > necessitated > > increasing the resources on the other servers. So as to experiment on > > this one. > > > > To the point! > > Building Apache 2.0 on this box requied cvsupping src/ports (2008-01-30). > > As the version of Apache 2.0 was 2.0.61 (has 2 security related issues). > > Current version: > > 2.0.63. Building/installing this version went w/o trouble. Ran as expected. > > I only made 1 mod from the default config/build: WITH_MPM?= threadpool. > > The original was: WITH_MPM?= prefork. My diong so also required: KQUEUE. > > Other than that, all was as-was. > > > > [snip] > > Regardless of the errors you reported, I believe changing the MPM is > a problem. Last time I tried Apache with the threaded worker MPM it > worked flawlessly. However PHP has issues because it isn't thread > safe. The only safe way to run the 2 together was to set the Apache > MPM back to the default (prefork).While I appreciate your insight regarding php5 not being "thread safe". I would argue that I am not seeing php5 using anthing regarding my Apache 2.0 build, except to ask whether it is 1.3 || 2. So, while you may be /absolutely/ correct about php5 not running well/at all with a threaded Apache. I'm still stumped as to why php5 refuses to build, and emits what appears to be errors in the php5 configure/make files. Point being; if I can get php5 to build/install. I might be able to make it "play nice" with a threaded Apache; and that would make /everyone/ happy. :)> Taking my disclaimer into account, I possibly just didn't figure out > how to make the 2 play nice, so I'd welcome info/pointers from others > who have managed to get threaded apache and PHP working together. > > Assuming no one pipes up and explains how to work around the PHP > threading issues, I'd recommend rebuilding apache with the default > MPM (shouldn't require any make variables defined). Verify it works > ok once installed and then try get PHP working again.I may try that. But I'm at a loss as to what that has to do with getting php5 to build. As (mentioned earlier) I am unable to find where php5 does anything more that to ask if I'm using Apache 1.3 || 2.> > I would also echo the recommendation of others to jump straight to > Apache 2.2(.8) if you're going to make a disruptive switch now > anyways. I have a personal step-by-step build guide for getting > Apache 2.2 and PHP5 working together if you're interested.Not going to happen - in the near future anyway. It's not unlike asking an Athiest to become a Jew. While it may be possible for one to make the change. It's a quantum leap. I've recently elaborated on this already. So I'll not repeat myself here. :)> > As to your reported errors, I can't really shed any light on them, sorry.Thank you very much for your thoughtful reply, and your generous offer Lawerence. :) --Chris> > Cheers, > Lawrence >-- panic: kernel trap (ignored)
Hi Chris, Firstly, a disclaimer: I'm not an expert so I might be behind the times on what I'm about to tell you... Chris H. wrote: > Hello all, > System: > FreeBSD 7.0-PRERELEASE i386 Wed Jan 16 18:39:53 PST 2008 > > Context: > After several failed attempts to get a /stable/ installation of > Apache13-ssl > and friends built and installed from source (see thread: > /usr/bin/objformat, for > more background). I chose to look at the possibility of using Apache > 2.0. I was > reluctant, as doing so would require migrating ~50 carefully crafted > conf files > which have evolved over many yrs. to be now seemingly impervious to > abuse, or > attack. I hadn't intended this server to become a guinea pig, but my ill > fated > attempts to install a stable copy of www/apache13-ssl from source > necessitated > increasing the resources on the other servers. So as to experiment on > this one. > > To the point! > Building Apache 2.0 on this box requied cvsupping src/ports (2008-01-30). > As the version of Apache 2.0 was 2.0.61 (has 2 security related issues). > Current version: > 2.0.63. Building/installing this version went w/o trouble. Ran as expected. > I only made 1 mod from the default config/build: WITH_MPM?= threadpool. > The original was: WITH_MPM?= prefork. My diong so also required: KQUEUE. > Other than that, all was as-was. > [snip] Regardless of the errors you reported, I believe changing the MPM is a problem. Last time I tried Apache with the threaded worker MPM it worked flawlessly. However PHP has issues because it isn't thread safe. The only safe way to run the 2 together was to set the Apache MPM back to the default (prefork). Taking my disclaimer into account, I possibly just didn't figure out how to make the 2 play nice, so I'd welcome info/pointers from others who have managed to get threaded apache and PHP working together. Assuming no one pipes up and explains how to work around the PHP threading issues, I'd recommend rebuilding apache with the default MPM (shouldn't require any make variables defined). Verify it works ok once installed and then try get PHP working again. I would also echo the recommendation of others to jump straight to Apache 2.2(.8) if you're going to make a disruptive switch now anyways. I have a personal step-by-step build guide for getting Apache 2.2 and PHP5 working together if you're interested. As to your reported errors, I can't really shed any light on them, sorry. Cheers, Lawrence