Summary: | graphics/webp build failure with a compiler error | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | vladimir.chukharev | ||||
Component: | Individual Port(s) | Assignee: | Po-Chuan Hsieh <sunpoet> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | mandree, olgeni | ||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | amd64 | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
vladimir.chukharev
2014-08-13 11:20:02 UTC
over to maintainer Hi, It only seems to happen on 9.3 (I first noticed it in poudriere) https://redports.org/buildarchive/20140813152701-50411/ The only difference I could see is that 9.3 has this line in the configure log: "checking whether cc supports -Wvla... yes" while 9.2 has: "checking whether cc supports -Wvla... no" Created attachment 145759 [details]
emmintrin.h fix for gcc 4.2 by dim@
dim@ said: This is a bug in gcc's emmintrin.h header. I have committed a fix to head in r269948, and I will merge it to stable/10 and stable/9 in three days. Meanwhile, please apply the attached diff to emmintrin.h in /usr/include/gcc/4.2 manually. *** Bug 192600 has been marked as a duplicate of this bug. *** Sunpoet, since I'm not sure if we'll have an erratum, and how fast they propagate to systems, may I propose: - please use either clang or a newer GCC version on the affected systems (9.3-RELEASE on amd64 for me). That avoids the broken header of gcc 4.2. Manual patching the header file as proposed helps me to build the port, thanks. Awaiting for MFC. sunpoet, can you see if it helps to copy the *patched* emmintrin.h header in the right WRKSRC directory? (In reply to Matthias Andree from comment #8) > sunpoet, can you see if it helps to copy the *patched* emmintrin.h header in > the right WRKSRC directory? Instead of shipping a patched emmintrin.h, we could: 1) Add CPPFLAGS+=-flax-vector-conversions 2) Add USES=compiler:c11 I would choose the latter. It works on 9.3-RELEASE, 10.0-RELEASE and 11-CURRENT. Either is fine for me. It should be fixed in r365223. Thanks! |