Summary: | dev-python/pyside2-5.15.1 : /.../cstddef: fatal error: stddef.h file not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Andrew Ammerlaan <andrewammerlaan> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andrewammerlaan, lssndrbarbieri, m.seifert, mgorny, sam, vaartis, waebbl-gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=835763 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
dev-python:pyside2-5.15.1:20201015-164049.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2 buildlog |
Description
Toralf Förster
2020-10-15 17:30:01 UTC
Created attachment 665897 [details]
emerge-info.txt
Created attachment 665900 [details]
dev-python:pyside2-5.15.1:20201015-164049.log
Created attachment 665903 [details]
emerge-history.txt
Created attachment 665906 [details]
environment
Created attachment 665909 [details]
etc.portage.tbz2
Created attachment 665912 [details]
logs.tbz2
Created attachment 665915 [details]
temp.tbz2
Created attachment 668210 [details]
buildlog
Ran into this as well. Same thing happened when compiling with gcc-10.2 Fixed by forcing dev-python/shiboken2 to be compiled with clang toolkit. Does this problem still occur? The ebuild appears to have some lines that look a lot like they are a workaround around this issue. Yes, that's why I CC-ed you — I can't build the new version. I'm confused, both versions build just fine for me, I didn't have to force clang on shiboken2. It compiled with clang instead of gcc automatically. It might be due to USE="default-compiler-rt default-libcxx" on clang. (In reply to Michał Górny from comment #15) > It might be due to USE="default-compiler-rt default-libcxx" on clang. Yes, this appears to be the case, with those flags I can reproduce this issue (CC="gcc" emerge -1 shiboken && emerge -1 pyside2 fails). Without those flags everything works fine, even if I force CC="gcc". I'm not sure what the best course of action is to fix this, we could force CC="clang", but that doesn't really make sense since it actually does compile with CC="gcc", just not if clang has those flags. I don't get why pyside2 insists on using clang in the first place. This is just asking for trouble. (In reply to Michał Górny from comment #17) > I don't get why pyside2 insists on using clang in the first place. This is > just asking for trouble. Shiboken2 apparently requires clang at runtime to do its thing, so my guess is that upstream simply assumes that everyone will be building shiboken2/pyside2 with clang as well and therefore doesn't really care about supporting anything other than clang. I have the same error. I resolve this by forcing both shiboken2 and pyside2 packages to be compiled with clang. Is this issue still valid for 5.15.5? |