Summary: | sci-electronics/kicad-4.0.2-r4 internal compiler error: Segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | segmentation fault <segmentation-fault> |
Component: | Current packages | Assignee: | Zoltan Puskas <zoltan> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build Log |
Description
segmentation fault
2016-09-04 15:20:30 UTC
This is not related to kicad. In the menatime, I've had the same error during compilation of webkit-gtk. This tipped me off to search in a different direction. All this time, I have been trying to run emerge @preserved-rebuild which started with webkit, then webkit-gtk, then kicad, then libreoffice...all of which (with the exception of webkit, I think) broke during compilation with internal compiler error, segmentation fault The 'preserved-rebuild' set was created by emerge during an upgrade of icu. I always upgrade icu with emerge -1uNDvt --verbose-conflicts --ask --with-bdeps=y --backtrack=30 \ dev-libs/icu \ $(qdepends -CQ icu | xargs -n 1 qatom | cut -d ' ' -f 1-2 | tr ' ' '/') \ dev-qt/qtwebkit \ $(qdepends -CQ qtwebkit | xargs -n 1 qatom | cut -d ' ' -f 1-2 | tr ' ' '/') \ $(qdepends -CQ boost | xargs -n 1 qatom | cut -d ' ' -f 1-2 | tr ' ' '/') \ app-text/texlive-core \ $(qdepends -CQ kpathsea | xargs -n 1 qatom | cut -d ' ' -f 1-2 | tr ' ' '/') \ app-text/poppler \ $(qdepends -CQ poppler | xargs -n 1 qatom | cut -d ' ' -f 1-2 | tr ' ' '/') ...adding a few more on the way, as needed. This is a monster that pulls in icu and all packages that depend on it qtwebkit and all packages that depend on it boost and all packages that depend on it texlive-core and all packages that depend on kpathsea poppler and all packages that depend on it because I know that, as soon as I upgrade icu, boost and poppler will start crying too - and then the others will follow suit. An upgrade of icu thus starts an avalanche of 400+ packages to be merged in one run on my system...:roll: The compilation error occurred with about 70 packages remaining in the queue. Not bad for a fully automatic dependency graph traversal... :-) Reason ====== Either the compiler itself, or some library used during compilation of these packages, needs dev-libs/boost which was also broken due to an upgrade of icu. In fact, boost itself was in the 'preserved-rebuild' set above, as tons of messages like the following were indicating: * - /usr/lib/libicudata.so.55 * - /usr/lib/libicudata.so.55.1 * used by /usr/lib/libboost_locale.so.1.56.0 (preserved) * used by /usr/lib/libboost_regex.so.1.56.0 (preserved) But portage obviously was thinking to re-merge boost *after* the above packages, i.e. after webkit-gtk, kicad and libreoffice - which, in this case, is wrong. Solution ======== Re-merge boost manually. I mean, you have just merged it, right? You have just upgraded from boost-1.56.0 to 1.61.0. It doesn't matter. icu came after that, which makes a recompilation of boost a priority 1 task! So do emerge -1 =dev-libs/boost-1.61.0 (notice the absence of '-u' option! To re-emerge, you should NOT use '-u', otherwise emerge will tell you that your package is up-to-date!) When boost is finished, rerun emerge @preserved-rebuild Now all is good. No internal compiler errors. No segmentation faults. All fine. :-) Please mark this as resolved (OK, I've done it myself :-)). |