| Summary: | CPPFLAGS should be explained in documentation | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Artem Leshchev <matshch> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | UNCONFIRMED --- | ||
| Severity: | minor | CC: | sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Sorry, but you misunderstood me in the bug. It's OK to set proper CPPFLAGS, but you shouldn't put CFLAGS or CXXFLAGS to CPPFLAGS I think it should be explained anyway so it will not be set to optimization flags. |
emerge --info shouldn't warn that CPPFLAGS is unset or make.conf documentation should explain for what it used. Now it can be confused with CXXFLAGS by usual user and set to ${CFLAGS}, what breaks some ebuilds. If it will be explained bugs like bug 518510 will not ever exist.