| Summary: | dev-util/cmake-2.4.8.ebuild gives wrong advices related to a non-existent libwww flag of dev-libs/xmlrpc-c-1.06.27 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | J.Borme <gentoo_bugs.nu_q5v> |
| Component: | New packages | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
We're at 2.6.2 now and the issue doesn't exist anymore. |
In some USE flags conbinations, cmake will output this: >>> Emerging (2 of 2) dev-util/cmake-2.4.8 [...] * cmake requires dev-libs/xmlrpc-c to be built with either the 'libwww' or * the 'curl' USE flag or both enabled. * Please re-emerge dev-libs/xmlrpc-c with USE="libwww" or USE="curl". Except there is no libwww flag for xmlrpc-c. The ebuild of current stable (dev-libs/xmlrpc-c-1.06.27) event explicitely de-activates libwww: econf --disable-wininet-client --enable-libxml2-backend --disable-libwww-client So AFAIU, it is needed to fix cmake ebuild in order not to suggest to use non-existent flags. Reproducible: Always