[PHP-DEV] Core files from apache/PHP without -X
Hi all, I need someone's help. I am trying desperately to find a segfault bug in PHP's output compression. I can not make it happen on a test server as it is just me hitting the site and what I do doesn't cause a segfault. So running it in gdb doesn't work. And using the httpd -X option to create a core file does not work for the same reason. I can, however, for the purpose of finding this bug, run a debug version of PHP on a production site for 3 minutes to get dozens of segfaults (I'll consider it downtime as the server load will pass over 350). But apache only creates a core file with the -X option. So I am stuck with either having lots of people hit it and cause the bug, but not be able to debug, or I can debug but not ever come across the bug I'm looking for. So is there any way to force Apache to dump core files? TIA -steve- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 4.3 ToDo
Georg,
That sounds great. There was a memory leak fix in that function for some
users of unbuffered queries that you might want to leave in. I propose
the following function which is also a placeholder/reminder for the
future:
/* {{{ _restore_connection_defaults
*/
static int _restore_connection_defaults(zend_rsrc_list_entry *rsrc
TSRMLS_DC)
{
php_mysql_conn *link;
/* check if its a persistent link */
if (Z_TYPE_P(rsrc) != le_plink)
return 0;
link = (php_mysql_conn *) rsrc-ptr;
/* Find the active result set and free it */
if (link-active_result_id) {
int type;
MYSQL_RES *mysql_result;
mysql_result = (MYSQL_RES *)
zend_list_find(link-active_result_id, type);
if (mysql_result type==le_result) {
zend_list_delete(link-active_result_id);
link-active_result_id = 0;
}
}
/* reset the persistent connection */
/*mysql_reset_connection(link-conn) -- TODO */
/* - not yet available in mysqllib */
/* - needed for bug #12513 */
return 0;
}
/* }}} */
PHP_RSHUTDOWN_FUNCTION(mysql)
{
zend_hash_apply(EG(persistent_list),
(apply_func_t)_restore_connection_defaults TSRMLS_CC);
...
I don't use unbuffered queries, so I really don't care either way. But
in my haste to get rid of that function, I don't want to be responsible
for the removal of other unrelated fixes.
Sincerely,
Steven Roussey
http://Network54.com/
-Original Message-
From: Georg Richter [mailto:[EMAIL PROTECTED]]
On Thursday 14 November 2002 19:58, Steven Roussey wrote:
Personally, I'd like to see the MySQL extension work again.
The issue: persistent connections are broken when used heavily.
Simple fix: _restore_connection_defaults() can be eliminated until
fixed
properly.
As discussed with Derick and Zak we will remove this stuff and wait
until
a
resolution inside the api is available (new api-function:
mysql_reset_connection). To unset all these things (and we can't unset
all)
needs more time than to establish a new connection.
Additionally we should add some warnings into the mysql_pconnect
chapter.
Regards
Georg
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] URL for segfaults
Does anyone have an idea on how to track down segfaults from a production Apache 1.3.27/PHP 4.2.3 server? If I could just figure out the URL for the page that died, it would go a very long way... My Apache error_log file is filled with this stuff and it is hurting the server's performance: [Thu Nov 21 08:10:11 2002] [notice] child pid 12850 exit signal Segmentation fault (11) [Thu Nov 21 08:10:17 2002] [notice] child pid 12908 exit signal Segmentation fault (11) [Thu Nov 21 08:10:18 2002] [notice] child pid 12593 exit signal Segmentation fault (11) [Thu Nov 21 08:10:18 2002] [notice] child pid 12525 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12815 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12518 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12454 exit signal Segmentation fault (11) [Thu Nov 21 08:10:20 2002] [notice] child pid 12600 exit signal Segmentation fault (11) [Thu Nov 21 08:10:21 2002] [notice] child pid 12645 exit signal Segmentation fault (11) [Thu Nov 21 08:10:22 2002] [notice] child pid 12569 exit signal Segmentation fault (11) [Thu Nov 21 08:10:25 2002] [notice] child pid 13051 exit signal Segmentation fault (11) [Thu Nov 21 08:10:25 2002] [notice] child pid 12633 exit signal Segmentation fault (11) [Thu Nov 21 08:10:28 2002] [notice] child pid 12714 exit signal Segmentation fault (11) [Thu Nov 21 08:10:31 2002] [notice] child pid 12461 exit signal Segmentation fault (11) [Thu Nov 21 08:10:37 2002] [notice] child pid 12658 exit signal Segmentation fault (11) [Thu Nov 21 08:10:39 2002] [notice] child pid 12565 exit signal Segmentation fault (11) [Thu Nov 21 08:10:42 2002] [notice] child pid 12524 exit signal Segmentation fault (11) [Thu Nov 21 08:10:43 2002] [notice] child pid 12922 exit signal Segmentation fault (11) [Thu Nov 21 08:10:49 2002] [notice] child pid 12875 exit signal Segmentation fault (11) [Thu Nov 21 08:10:52 2002] [notice] child pid 12508 exit signal Segmentation fault (11) [Thu Nov 21 08:10:58 2002] [notice] child pid 12656 exit signal Segmentation fault (11) [Thu Nov 21 08:10:59 2002] [notice] child pid 13076 exit signal Segmentation fault (11) [Thu Nov 21 08:10:59 2002] [notice] child pid 12826 exit signal Segmentation fault (11) [Thu Nov 21 08:10:59 2002] [notice] child pid 12659 exit signal Segmentation fault (11) [Thu Nov 21 08:11:01 2002] [notice] child pid 12812 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12982 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12780 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12740 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12540 exit signal Segmentation fault (11) [Thu Nov 21 08:11:04 2002] [notice] child pid 12778 exit signal Segmentation fault (11) [Thu Nov 21 08:11:04 2002] [notice] child pid 12603 exit signal Segmentation fault (11) [Thu Nov 21 08:11:10 2002] [notice] child pid 13079 exit signal Segmentation fault (11) [Thu Nov 21 08:11:11 2002] [notice] child pid 13080 exit signal Segmentation fault (11) [Thu Nov 21 08:11:12 2002] [notice] child pid 12823 exit signal Segmentation fault (11) [Thu Nov 21 08:11:13 2002] [notice] child pid 12712 exit signal Segmentation fault (11) [Thu Nov 21 08:11:13 2002] [notice] child pid 12455 exit signal Segmentation fault (11) [Thu Nov 21 08:11:14 2002] [notice] child pid 12701 exit signal Segmentation fault (11) [Thu Nov 21 08:11:23 2002] [notice] child pid 12672 exit signal Segmentation fault (11) Sincerely, Steven Roussey http://Network54.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] URL for segfaults
No. And I wish access_log logged requests at the beginning of a request and had the child pid. There has to be some way of discovering or logging URLs and seeing if they complete without a segfault, at which point I'd look for those that did not complete. Surely I'm missing something simple... Sincerely, Steven Roussey http://Network54.com/ -Original Message- From: Vergoz Michael [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 8:47 am To: Steven Roussey; [EMAIL PROTECTED] Subject: Re: [PHP-DEV] URL for segfaults Hi ! Did you have some stranges URL request in access_log ? Michael- - Original Message - From: Steven Roussey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 21, 2002 5:39 PM Subject: [PHP-DEV] URL for segfaults Does anyone have an idea on how to track down segfaults from a production Apache 1.3.27/PHP 4.2.3 server? If I could just figure out the URL for the page that died, it would go a very long way... My Apache error_log file is filled with this stuff and it is hurting the server's performance: [Thu Nov 21 08:10:11 2002] [notice] child pid 12850 exit signal Segmentation fault (11) [Thu Nov 21 08:10:17 2002] [notice] child pid 12908 exit signal Segmentation fault (11) [Thu Nov 21 08:10:18 2002] [notice] child pid 12593 exit signal Segmentation fault (11) [Thu Nov 21 08:10:18 2002] [notice] child pid 12525 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12815 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12518 exit signal Segmentation fault (11) -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] URL for segfaults
Yes. Ideally such that you can grep for the failed URLs. I can see this as being very helpful to a lot of people. Debug modes don't work for production servers and it is only there that it is showing itself. BTW - Easy for you maybe! Sincerely, Steven Roussey http://Network54.com/ -Original Message- From: Ivan Ristic [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 9:24 am To: Steven Roussey Cc: 'Vergoz Michael'; [EMAIL PROTECTED] Subject: Re: [PHP-DEV] URL for segfaults Steven Roussey wrote: No. And I wish access_log logged requests at the beginning of a request and had the child pid. It would be very easy to write a custom module to log that at the beginning of the request. Would that help? Ivan -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] URL for segfaults
Well, I think I found the cause if not the cure. I posted a bug report yesterday about zLib (http://bugs.php.net/?id=20535) that seems to be the culprit for another crash. Since our output compression uses it as well, I tried turning output compression off. No more segfaults. Unfortunately, I'll have to turn it back on and live with the segfaults for now until I find the problem with zLib 1.1.4. :( Luckily, I happen to have one string saved away that I know crashes it. Hopefully it will be enough to figure things out. Sincerely, Steven Roussey http://Network54.com/ On Thu, 2002-11-21 at 09:39, Steven Roussey wrote: Does anyone have an idea on how to track down segfaults from a production Apache 1.3.27/PHP 4.2.3 server? If I could just figure out the URL for the page that died, it would go a very long way... My Apache error_log file is filled with this stuff and it is hurting the server's performance: [Thu Nov 21 08:10:11 2002] [notice] child pid 12850 exit signal Segmentation fault (11) [Thu Nov 21 08:10:17 2002] [notice] child pid 12908 exit signal Segmentation fault (11) [Thu Nov 21 08:10:18 2002] [notice] child pid 12593 exit signal Segmentation fault (11) [Thu Nov 21 08:10:18 2002] [notice] child pid 12525 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12815 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12518 exit signal Segmentation fault (11) [Thu Nov 21 08:10:19 2002] [notice] child pid 12454 exit signal Segmentation fault (11) [Thu Nov 21 08:10:20 2002] [notice] child pid 12600 exit signal Segmentation fault (11) [Thu Nov 21 08:10:21 2002] [notice] child pid 12645 exit signal Segmentation fault (11) [Thu Nov 21 08:10:22 2002] [notice] child pid 12569 exit signal Segmentation fault (11) [Thu Nov 21 08:10:25 2002] [notice] child pid 13051 exit signal Segmentation fault (11) [Thu Nov 21 08:10:25 2002] [notice] child pid 12633 exit signal Segmentation fault (11) [Thu Nov 21 08:10:28 2002] [notice] child pid 12714 exit signal Segmentation fault (11) [Thu Nov 21 08:10:31 2002] [notice] child pid 12461 exit signal Segmentation fault (11) [Thu Nov 21 08:10:37 2002] [notice] child pid 12658 exit signal Segmentation fault (11) [Thu Nov 21 08:10:39 2002] [notice] child pid 12565 exit signal Segmentation fault (11) [Thu Nov 21 08:10:42 2002] [notice] child pid 12524 exit signal Segmentation fault (11) [Thu Nov 21 08:10:43 2002] [notice] child pid 12922 exit signal Segmentation fault (11) [Thu Nov 21 08:10:49 2002] [notice] child pid 12875 exit signal Segmentation fault (11) [Thu Nov 21 08:10:52 2002] [notice] child pid 12508 exit signal Segmentation fault (11) [Thu Nov 21 08:10:58 2002] [notice] child pid 12656 exit signal Segmentation fault (11) [Thu Nov 21 08:10:59 2002] [notice] child pid 13076 exit signal Segmentation fault (11) [Thu Nov 21 08:10:59 2002] [notice] child pid 12826 exit signal Segmentation fault (11) [Thu Nov 21 08:10:59 2002] [notice] child pid 12659 exit signal Segmentation fault (11) [Thu Nov 21 08:11:01 2002] [notice] child pid 12812 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12982 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12780 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12740 exit signal Segmentation fault (11) [Thu Nov 21 08:11:03 2002] [notice] child pid 12540 exit signal Segmentation fault (11) [Thu Nov 21 08:11:04 2002] [notice] child pid 12778 exit signal Segmentation fault (11) [Thu Nov 21 08:11:04 2002] [notice] child pid 12603 exit signal Segmentation fault (11) [Thu Nov 21 08:11:10 2002] [notice] child pid 13079 exit signal Segmentation fault (11) [Thu Nov 21 08:11:11 2002] [notice] child pid 13080 exit signal Segmentation fault (11) [Thu Nov 21 08:11:12 2002] [notice] child pid 12823 exit signal Segmentation fault (11) [Thu Nov 21 08:11:13 2002] [notice] child pid 12712 exit signal Segmentation fault (11) [Thu Nov 21 08:11:13 2002] [notice] child pid 12455 exit signal Segmentation fault (11) [Thu Nov 21 08:11:14 2002] [notice] child pid 12701 exit signal Segmentation fault (11) [Thu Nov 21 08:11:23 2002] [notice] child pid 12672 exit signal Segmentation fault (11) Sincerely, Steven Roussey http://Network54.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.3 ToDo
Personally, I'd like to see the MySQL extension work again. The issue: persistent connections are broken when used heavily. Simple fix: _restore_connection_defaults() can be eliminated until fixed properly. So if the simple fix is implemented then all users of MySQL not using transactions will work as before, whether using persistent connections or not. Standard working behavior. Which is not currently the case. User's of MySQL using trasactions will not be able to use persistent connections. This has always been the case, but the trial fix for this has broken persistent connections for everyone. :( -steve- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Changes to PHP/MySQL extension
I have had problems with PHP and MySQL and have made some changes. First
off, in http://bugs.php.net/bug.php?id=19529 MySQL is complaining about
things not being cleaned up. This is because any query that returns
results (which one's don't -- any?) must get them.
In case of an unbuffered query, we need to eat the rest of the rows
before exiting (like we do when a new query is run when an old
unbuffered query was not finished). I removed the warning in this case,
but you all can change it as you please.
The case that is hitting me (and EVERYONE out there using persistent
connections with current revs) is that there is a rollback. But there is
nothing to get the results of the rollback. This means, that the next
script to use this persistent connection will generally fail on the
first query, but might do alright on the others. For this reason, I
recommend anyone use PHP 4.2.3 (maybe later versions as well) to turn
off persistent connections for now.
Also, in CVS there is something to reset AUTOCOMMIT. It also did not
clean up and that causes additional issues. I removed it rather than
fixed it. Who says AUTOCOMMIT=1 should be the default for a certain
server? That is user configurable on the server side. Personally, I like
the idea of resetting all the variables that might have been changed
(including that one). There are a lot. No good way to do right now.
Oh, what else? Ah.. the code in CVS for mysql.connection.timeout. That
rocks! However, it sets the default to zero and then checks for -1 as a
sign not to include the option. Oops. So the default timeout value is
set to nothing when the user doesn't do anything. That is a
unpredictable change in behavior.
I have some changes below. My first time even looking at this code, so
look for any mistakes.
static int _restore_connection_defaults(zend_rsrc_list_entry *rsrc
TSRMLS_DC)
{
php_mysql_conn *link;
charquery[128];
charuser[128];
charpasswd[128];
/* check if its a persistent link */
if (Z_TYPE_P(rsrc) != le_plink)
return 0;
link = (php_mysql_conn *) rsrc-ptr;
if (link-active_result_id) do {
int type;
MYSQL_RES *mysql_result;
mysql_result = (MYSQL_RES *)
zend_list_find(link-active_result_id, type);
if (mysql_result type==le_result) {
if (!mysql_eof(mysql_result)) {
while (mysql_fetch_row(mysql_result));
}
zend_list_delete(link-active_result_id);
link-active_result_id = 0;
}
} while(0);
/* rollback possible transactions */
strcpy (query, ROLLBACK);
if (mysql_real_query(link-conn, query, strlen(query)) !=0 ) {
MYSQL_RES *mysql_result=mysql_store_result(link-conn);
mysql_free_result(mysql_result);
}
/* unset the current selected db */
#if MYSQL_VERSION_ID 32329
strcpy (user, (char *)(link-conn)-user);
strcpy (passwd, (char *)(link-conn)-passwd);
mysql_change_user(link-conn, user, passwd, );
#endif
return 0;
}
And change the two copies of this:
if (connect_timeout != -1)
to
if (connect_timeout = 0)
My 2 cents for the day.
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: Proposed updates and extensions to the MySQL extension
Allow persistent connections to be closed and 'pruned'. I'm unclear as to the reason for this one. Unless people are using lots of different username/password combos in which case the connections should not be persistent. Persistent connections were made to make speed up repetitive identical connections as is often found in web applications (and where end user security is often then handled by the app, not the database). [PHP Manual: Chapter 22: ...In particular, they do not give you an ability to open 'user sessions' on the same SQL link...] However, I'd like to add a item to the list proposed by Zac and Monty: Persistent connection pools that are _per server_ rather than _per process_. Perhaps it would be activated if the mm module were included. It amazes me that this difference is still not explained in the manual. The only reference is the configuration of php.ini. Things like mysql.max_persistent are also _per process_ (duly noted in that part of the manual), but have a completely different meaning than might be usually expected. For example, mysql.max_persistent effectively has to do with the max number of different server/user/pass combinations of persistent connections that that process makes. For a web app connecting to only one MySQL server with the same user/pass, this parameter is meaningless. This, of course, is important only to Apache servers where you must multiply the per process items above by the max number of child servers Apache will run. Sincerely, Steven Roussey http://Network54.com/?pp=e -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] What happened to lxr.php.net?
What happened to lxr.php.net? Will it return? Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] 4.0.5 Comments change (leads to inappropriate parseerror based on contents of comments)
OK.
Here is an example of why it causes problems: We had some lines of code like
this:
echo ("table width=100%");
works ok. But then we comment out the that line:
// echo ("table width=100%");
it now dies.
You might make a note in the NEWS section if it is not already there. I'll
get everyone here to hand convert all the ASP tags to more PHP like tags
(and maybe eliminate short tags too) and then turn those options off so the
(very common) scenario above doesn't drive people nuts later...
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
This was fixed to be consistent with ?.
One line comments end at a new line or at a closing bracket (? or %)
Andi
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Object Constructors in PHP
Don't ask why it is this way, but say we have these files:
::
inc1.php
::
?
class base {
function ForumStyle() {
echo ('hi');
}
}
?
::
inc2.php
::
?
class ForumStyle extends base {
var $temp;
}
?
::
inc3.php
::
?
class Outline_ForumStyle extends ForumStyle {
function Outline_ForumStyle () {
$this-ForumStyle();
}
}
?
::
test.php
::
?
include ('inc1.php');
include ('inc2.php');
include ('inc3.php');
$i = new Outline_ForumStyle();
It runs fine printing 'hi' (though not with APC, but fine with Zend Cache).
BUT, What _should_ happen?
BTW: For the APC list, this is a test case of bug #3. Use the apc_gui to
look at inc3.php
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: About arg_separator..
Hi, Ax my last message. We deal with the ; in a URL in Apache before going to PHP. However, 4.0.5 still breaks our site. It appears to be related to class inheritance and/or included files. I'm working on a specific test case right now to show the problem... Be back in an hour or so... Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] 4.0.5 Comments change (leads to inappropriate parse error based oncontents of comments)
Hi,
I found our problem. In 4.0.5, comments seem to be parsed differently. We
have ASP style tags enabled so we can use % as well as ?. But we had
comments like this:
?
//asdfasdf%asdfasdf
echo('');
?
4.0.5 would ignore the whole line. 4.0.5 still parses it for open and
close tags. The lines above get handled differently from 4.0.4 to 4.0.5. It
is hard to track if the comment is inside a class, because there is no parse
error until the end of the file, and the code is not spit out like HTML (as
in the example above) because it is compiling the file. I think this is a
bug. We can clean up our code to fix it (and will), but
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] RE: 4.0.5RC1 static build with Apache 1.3.19 problem
RC2 builds fine with my rebuild script (always good for testing :). Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e -Original Message- From: Steven Roussey [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 6:40 PM To: [EMAIL PROTECTED] Subject: RE: [PHP-DEV] RE: 4.0.5RC1 static build with Apache 1.3.19 problem Yes, I have tried it both ways. I configure Apache a second time after making php and it still does not work. :( Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e Subject: Re: [PHP-DEV] RE: 4.0.5RC1 static build with Apache 1.3.19 problem Did you configure Apache after you did the make install from PHP? In the PHP directory run make install-sapi and see that PHP copies everything to the right directory. Andi At 07:12 PM 3/16/2001 -0800, Steven Roussey wrote: Subject: 4.0.5RC1 static build with Apache 1.3.19 problem Also happens in Apache 1.3.12 Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e cd apache_1.3.12 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite cd .. cd php-4.0.5RC1 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --with-mysql --with-xml --with-dom --with-zlib --with-gd \ --with-openssl --with-sablot --with-apache=../apache_1.3.12 --enable-inline- optimization make make install cd .. cd apache_1.3.12 make === src/modules/php4 make[4]: *** No rule to make target `all'. Stop. make[3]: *** [all] Error 1 make[2]: *** [subdirs] Error 1 make[2]: Leaving directory `/home/network54/webserver/apache_1.3.12/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/home/network54/webserver/apache_1.3.12' make: *** [build] Error 2 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] wget --passive-ftp http://www.openssl.org/source/openssl-0.9.6.tar.gz gunzip openssl-0.9.6.tar.gz | tar xvf - cd openssl-0.9.6 make clean CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./config make make install cd .. wget --passive-ftp ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/libxml2-2.3.4.tar.gz gunzip libxml2-2.3.4.tar.gz | tar xvf - cd libxml2-2.3.4 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --disable-corba make make install cd .. wget --passive-ftp http://ftp1.sourceforge.net/expat/expat-1.95.1.tar.gz gunzip expat-1.95.1.tar.gz | tar xvf - cd expat-1.95.1 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure make make install cd .. wget --passive-ftp http://www.gingerall.com/perl/rd?url=sablot/Sablot-0.51.tar.gz gunzip Sablot-0.51.tar.gz | tar xvf - cd Sablot-0.51 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure make make install cd .. wget --passive-ftp http://freshmeat.net/projects/zlib/altdownload/zlib.tar.gz gunzip zlib.tar.gz | tar xvf - cd zlib-1.1.3 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --shared make make install cd .. wget --passive-ftp http://httpd.apache.org/dist/apache_1.3.19.tar.gz gunzip apache_1.3.19.tar.gz | tar xvf - cd apache_1.3.19 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite cd .. wget --passive-ftp http://www.php.net/distributions/php-4.0.5RC2.tar.gz gunzip php-4.0.5RC2.tar.gz | tar xvf - cd php-4.0.5RC2 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --with-mysql --with-xml --with-dom --with-zlib --with-gd \ --with-openssl --with-sablot --with-apache=../apache_1.3.19 --enable-inline-optimization make make install cd .. cd apache_1.3.19 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite make make install cd .. cd php-4.0.5RC2 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --with-mysql --with-xml --with-dom --with-zlib --with-gd \ --with-openssl --with-sablot --enable-inline-optimization make make install cd .. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] RE: 4.0.5RC1 static build with Apache 1.3.19 problem
Yes, I have tried it both ways. I configure Apache a second time after making php and it still does not work. :( Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e Subject: Re: [PHP-DEV] RE: 4.0.5RC1 static build with Apache 1.3.19 problem Did you configure Apache after you did the make install from PHP? In the PHP directory run make install-sapi and see that PHP copies everything to the right directory. Andi At 07:12 PM 3/16/2001 -0800, Steven Roussey wrote: Subject: 4.0.5RC1 static build with Apache 1.3.19 problem Also happens in Apache 1.3.12 Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e cd apache_1.3.12 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite cd .. cd php-4.0.5RC1 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --with-mysql --with-xml --with-dom --with-zlib --with-gd \ --with-openssl --with-sablot --with-apache=../apache_1.3.12 --enable-inline- optimization make make install cd .. cd apache_1.3.12 make === src/modules/php4 make[4]: *** No rule to make target `all'. Stop. make[3]: *** [all] Error 1 make[2]: *** [subdirs] Error 1 make[2]: Leaving directory `/home/network54/webserver/apache_1.3.12/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/home/network54/webserver/apache_1.3.12' make: *** [build] Error 2 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] 4.0.5RC1 static build with Apache 1.3.19 problem
We use a static (non-DSO) version of apache for top speed. At the bottom of the message is a list of commands we use to create a web server on a new machine (assuming the .tar.gz files are there). Our main servers use apache 1.3.12 and PHP 4.0.4pl1. This test updates them to Apache 1.3.19 and php-4.0.5RC1 and fails to compile apache in the php module: #configure for apache: CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite make ... === src/modules/php4 make[4]: *** No rule to make target `all'. Stop. make[3]: *** [all] Error 1 make[2]: *** [subdirs] Error 1 make[2]: Leaving directory `/home/network54/webserver/apache_1.3.19/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/home/network54/webserver/apache_1.3.19' make: *** [build] Error 2 Not all php modules are the most up-to-date, but php compiles and installs just fine. Here is the relevant part from php's make install: make[1]: Entering directory `/home/network54/webserver/php-4.0.5RC1' mkdir -p /home/network54/webserver/apache_1.3.19/src/modules/php4; cp libs/libphp4.a /home/network54/webserver/apache_1.3.19/src/modules/php4/libmodphp4.a; cp /home/network54/webserver/php-4.0.5RC1//sapi/apache/mod_php4.* sapi/apache/libphp4.module /home/network54/webserver/apache_1.3.19/src/modules/php4; cp ./sapi/apache/apMakefile.tmpl /home/network54/webserver/apache_1.3.19/src/modules/php4/Makefile.tmpl; cp ./sapi/apache/apMakefile.libdir /home/network54/webserver/apache_1.3.19/src/modules/php4/Makefile.libdir After the failure of apache's make above, I did a 'ls' on the dir: ls src/modules/php4 Makefile.libdir Makefile.tmpl libmodphp4.a libphp4.module mod_php4.c mod_php4.exp mod_php4.h mod_php4.lo mod_php4.o No Makefile. Is this an error with PHP or Apache? Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e Build commands given .tar.gz files: gunzip openssl-0.9.6.tar.gz | tar xvf - cd openssl-0.9.6 make clean CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./config make make install cd .. gunzip libxml2-2.2.11.tar.gz | tar xvf - cd libxml2-2.2.11 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --disable-corba make make install cd .. gunzip expat-1.95.1.tar.gz | tar xvf - cd expat-1.95.1 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure make make install cd .. gunzip Sablot-0.50.tar.gz | tar xvf - cd Sablot-0.50 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure make make install cd .. gunzip zlib.tar.gz | tar xvf - cd zlib-1.1.3 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --shared make make install cd .. gunzip apache_1.3.19.tar.gz | tar xvf - cd apache_1.3.19 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite cd .. gunzip php-4.0.5RC1.tar.gz | tar xvf - cd php-4.0.5RC1 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --with-mysql --with-xml --with-dom --with-zlib --with-gd \ --with-openssl --with-sablot --with-apache=../apache_1.3.19 --enable-inline- optimization make make install cd .. cd apache_1.3.19 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite make make install -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: 4.0.5RC1 static build with Apache 1.3.19 problem
Subject: 4.0.5RC1 static build with Apache 1.3.19 problem Also happens in Apache 1.3.12 Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e cd apache_1.3.12 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure \ --activate-module=src/modules/php4/libphp4.a --enable-module=rewrite cd .. cd php-4.0.5RC1 CC=gcc CFLAGS="-O6 -march=i686 " CXX=gcc CXXFLAGS="-O6 -march=i686 " \ ./configure --with-mysql --with-xml --with-dom --with-zlib --with-gd \ --with-openssl --with-sablot --with-apache=../apache_1.3.12 --enable-inline- optimization make make install cd .. cd apache_1.3.12 make === src/modules/php4 make[4]: *** No rule to make target `all'. Stop. make[3]: *** [all] Error 1 make[2]: *** [subdirs] Error 1 make[2]: Leaving directory `/home/network54/webserver/apache_1.3.12/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/home/network54/webserver/apache_1.3.12' make: *** [build] Error 2 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
