| Summary: | sys-libs/libstdc++-v3-3.3.6 build failed: trying to use system CPPFLAGS with self-compiled xgcc (gcc 3.3.6) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Denis Kaganovich <mahatma> |
| Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | libstdc++-v3-3.3.6.ebuild patch | ||
Created attachment 200847 [details, diff]
libstdc++-v3-3.3.6.ebuild patch
Why are you putting those flags in there in the first place? CPPFLAGS are flags that are passed to the preprocessor. Those flags aren't preprocessor flags. Are you mixing it up with CXXFLAGS? |
sys-libs/libstdc++-v3-3.3.6 build failed: trying to use unfiltered system-wide CPPFLAGS with self-compiled xgcc (gcc 3.3.6). To reproduce just add any "new" gcc flag into CPPFLAGS (-msse4.1 or -fivopts or -ftree-loop-linear): CPPFLAGS="-ftree-loop-linear" emerge -1 libstdc++-v3 Solution: add 'CPPFLAGS=""' or 'CPPFLAGS="${CFLAGS}"' into "emake" commandline. (attaching in patch form) Reproducible: Always