| Summary: | app-portage/gentoolkit - euse -i c++0x | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Denys Duchier <denys.duchier> |
| Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 346443 | ||
The USE-flag is masked in the profile (can cause problems). You have to unmask it. (In reply to comment #1) > The USE-flag is masked in the profile (can cause problems). You have to > unmask it. Assuming M means masked. I still don't understand the output of euse: why the +? why the E? why the G? (In reply to comment #2) > I still don't understand the output of euse: why > the +? why the E? why the G? "man euse" should help. (In reply to comment #3) > (In reply to comment #2) > > I still don't understand the output of euse: why > > the +? why the E? why the G? > > "man euse" should help. dude, I have read the man page. why does euse think that the flag is seen active by portage (+)? why does it think that the flag is enabled in the environment (E)? it definitely isn't. why does it think the flag is enabled in make.globals G)? it isn't. This has been fixed in the following commit: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=79135c7585402eadeb9e06cbf3138f0d191b15d9 The '+' characters in the useflag were causing problems with a regular expression in the code. This was released with gentoolkit-0.3.0.6-r2 |
the new flag c++0x (e.g. used by qt packages) is not properly handled by euse. global use flags (searching: c++0x) ************************************************************ no matching entries found local use flags (searching: c++0x) ************************************************************ [+E G M] x11-libs/qt-assistant:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-core:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-dbus:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-declarative:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-demo:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-gui:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-multimedia:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-opengl:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-openvg:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-phonon:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-qt3support:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-script:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-sql:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-svg:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-test:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-webkit:c++0x - Build Qt using the C++11 standard: [+E G M] x11-libs/qt-xmlpatterns:c++0x - Build Qt using the C++11 standard: but the flag is not actually active (none of the newly compiled qt packages has been built with it). (btw, I have no idea what M means: it's not documented).