Summary: | dev-qt/qtwebkit fails to compile with -std=gnu11/-std=gnu++11 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | qtwebkit-4.8.5:20150308-022904.log |
Description
Agostino Sarubbo
2015-03-09 09:40:55 UTC
Created attachment 398484 [details]
qtwebkit-4.8.5:20150308-022904.log
build log
You're not supposed to add -std=foo options to your CXXFLAGS. (In reply to Davide Pesavento from comment #2) > You're not supposed to add -std=foo options to your CXXFLAGS. correct, you should never add -std=anything to the build system. I think ago misunderstood the tracker. @ago. packages written in c++ may insist on adhering to c++11 standards, eg. chromium does. if they do, then we have no choice and build accordingly. the result are packages whose abi may be mismatched with other c++ stuff on the filesystem. this mismatch can happen because 1) the other stuff was compiled with c++98 or 2) we switch up compilers. we hit these every once in a while, but we should go out of our way to find them. the problem isn't in the packages. its in how we do toolchains and portage stuff. what we need to do is track these mismatches and trigger a rebuild via portage. we're still not sure how to do that. |