Bug #18012 Updated: Info provided by phpinfo() does not update upon re-compiles

ID: 18012 Updated by: h3+php@x-maru.org Reported By: h3+php@x-maru.org Status: Closed Bug Type: PHP options/info functions Operating System: Linux PHP Version: 4.2.1 New Comment: It's so amazing- submit bug, go to bed, wake up- bug fixed! Thank you so much for your time with this relatively trivial bug. I am mostly concerned with the ./configure line as I use it to remind me how to do builds. As for the apache block of the phpinfo() output not being updated - the correct information appears elsewhere under the SERVER_SOFTWARE variable, so the correct information is indeed available somewhere. Thanks again. Previous Comments: ------------------------------------------------------------------------ [2002-06-27 06:03:09] sander@php.net Hm... that amazon url doesn't belong there :) ------------------------------------------------------------------------ [2002-06-27 06:02:27] sander@php.net I've fixed the configure-line problem in CVS, but the Apache problem is harder: the Apache version is defined in http://www.amazon.de/exec/obidos/ASIN/3826608283/ httpd.h, provided with Apache. There's no clean way of checking whether it has been changed since the last 'make'. If you have any ideas how to do this, or if you notice any other outdated phpinfo() entries, feel free to reopen this report. Thanks for your report. ------------------------------------------------------------------------ [2002-06-27 04:48:43] h3+php@x-maru.org Information provided by phpinfo() is not accurate when php is recompiled. An example: php is originally built against apache-1.3.24 with modules A, B, and C. Later, it is rebuilt against apache-1.3.26 with A, B, C, and D. phpinfo() continues to output information from the first build, ie the httpd in use is apache-1.3.24 and the ./configure line includes A, B, and C only. This info is corrected if the rebuild is from scratch (make clean, rm config.cache, etc). However, my expectation is this information should be accurate for every build, without having to do a completely clean build. This has been a bug for quite sometime, and is not specific to 4.2.1. I don't recall a version that didn't have this problem. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=18012&edit=1