Summary: | Error running ebuild /path/mod_php-4.3.2.ebuild config | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Keith Edmunds <keith> |
Component: | [OLD] Development | Assignee: | PHP Bugs <php-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Keith Edmunds
2003-07-11 03:54:23 UTC
Re-install mod_php-4.3.2 or just copy the current mod_php-4.3.2.ebuild to your DB copy. This is because a global change was made to the PHP eclass to make it sane. I have an automated build/configure script which now dies every time it tries to configure mod_php. If I understand you correctly, the steps to configure mod_php are: 1. Install mod_php 2. Run the configure script 3. Let it fail 4. Reinstall mod_php 5. Rerun the configure script That isn't a great solution. What can I do so that the configure script runs correctly at the first invocation? Thanks All you have to do it overwrite /var/db/pkg/dev-php/mod_php-4.3.2/mod_php-4.3.2.ebuild with the updated version. Just do: cp /usr/portage/dev-php/mod_php/mod_php-4.3.2.ebuild /var/db/pkg/dev-php/mod_php-4.3.2/mod_php-4.3.2.ebuild Then it will stop complaining. The sole problem here is that you have an outdated copy of the ebuild, without a critical change. |