Summary: | phpconfig make assumption about extensions directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Neil Darlow <neil> |
Component: | [OLD] Development | Assignee: | Stuart Herbert (RETIRED) <stuart> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | sven.jacobs, wendallc |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Neil Darlow
2005-06-14 06:07:31 UTC
Thanks for the bug report. I need to update the phpconfig package to support four combinations: a) without debug, no thread safety b) without debug, thread safety c) with debug, no thread safety d) with debug, thread safety Best regards, Stu As a temporary work around, interrupt the build of mod_php (after configure), and sync the following files from /var/tmp/portage/mod_php-5.0.4/work/php-5.0.4 (which contain your configure options) with their installed counterparts. /usr/bin/php-config /usr/include/php/main/build-defs.h /usr/include/php/main/php_config.h This will allow compontents that check these includes to build correctly (eaccelerator) until a new ebuild is released. In order to correct this package, might it be an idea to allow configure to run with the options specified in the use flags, *then* copy the data to the include directory? My workaround is to supply the mkconfig USE flag to mod_php and use ebuild install to create the phpconfig-5.0.4.tar.bz2 file then emerge php-config using that file. The phpconfig ebuild seems to be out of sync. I am running PHP 5.1 beta 2 but the phpconfig ebuild still installs for PHP 5.1 beta 1. This leads to wrong assumptions about for example the extension_dir when PEAR modules use php-config to configure themselves while installing. Closing this since dev-php/phpconfig is no more in the tree, as actual dev-lang/php does this himself and sets the correct extension-dir in php.ini (don't forget to run etc-update after newinstall!). Best regards, CHTEKK. |