Bug 640368 – sys-devel/gcc-6.3.0 , sys-libs/glibc-2.26 - In file included from .../work/gcc-6.3.0/libgcc/unwind-dw2.c:401:0: ./md-unwind-support.h: In function ‘x86_fallback_frame_state’: ./md-unwind-support.h:141:18: error: field ‘uc’ has incomplete type

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description rnddim 2017-12-09 13:05:09 UTC]

Created attachment 509022 [details]
emerge --info '=sys-devel/gcc-6.3.0::gentoo'

Trying to recompile gcc-6.3.0 while updating my @world for the profile update causes the build to fail due to an incomplete type. My guess is this could either be caused by the version of gcc being used to compile it (gcc-7.2.0), or by the +pie USE flag from the profile update.

The result of emerge -pqv :

[ebuild   R   ] sys-devel/gcc-6.3.0  USE="cxx fortran (multilib) nls nptl openmp pch (pie*) sanitize ssp vtv (-altivec) (-awt) -cilk -debug -doc (-fixed-point) (-gcj) -go -graphite (-hardened) (-jit) (-libssp) -mpx -objc -objc++ -objc-gc -pgo -regression-test -vanilla"

[Comment 1 rnddim 2017-12-09 13:05:57 UTC]

Created attachment 509024 [details]
build.log.xz

[Comment 2 Andreas K. Hüttel 2017-12-17 23:05:36 UTC]

does gcc-6.4 build for you?

[Comment 3 Steve Arnold 2017-12-22 19:36:43 UTC]

Same error trying to rebuild gcc-5.4.0 with 6.4.0 (I know, but pdftk apparently needs gcc-5 with gcj ??) after setting the new profile.

[Comment 4 Steve Arnold 2017-12-22 21:17:28 UTC]

Created attachment 511494 [details, diff]
cross-build patch for ucontext change

partial patch for cross-builds, doesn't help with native x86_64...

[Comment 5 Andreas K. Hüttel 2018-01-01 21:21:55 UTC]

I'm pretty sure we tested building gcc-5 with gcc-6 and glibc-2.26 ... now the question is, why does it fail here and work for me? 

(Just started another test build.)

(The ucontext change is specific to glibc-2.26.)

[Comment 6 Gerrit Kühn 2018-08-07 14:03:14 UTC]

Are there any news on this? I see the same issue and cannot rebuild gcc-4.8.5 nor gcc-4.7.4. Neither gcc-6.4 nor gcc 5.4 nor gcc-4.9.4 can build these.

[Comment 7 Sergei Trofimovich (RETIRED) 2018-08-07 18:47:38 UTC]

(In reply to Gerrit Kühn from comment #6)
> Are there any news on this? I see the same issue and cannot rebuild
> gcc-4.8.5 nor gcc-4.7.4. Neither gcc-6.4 nor gcc 5.4 nor gcc-4.9.4 can build
> these.

Please attach build.log for failed gcc:6.4.0.

[Comment 8 Gerrit Kühn 2018-08-10 07:27:07 UTC]

(In reply to Sergei Trofimovich from comment #7)

> Please attach build.log for failed gcc:6.4.0.

Sorry? gcc:6.4.0 compiles just fine. I cannot rebuild gcc:4.8.5 nor gcc:4.7.4 using gcc:6.4.0. Which build logs do you need?

[Comment 9 Sergei Trofimovich (RETIRED) 2018-08-10 21:29:57 UTC]

(In reply to Gerrit Kühn from comment #8)
> (In reply to Sergei Trofimovich from comment #7)
> 
> > Please attach build.log for failed gcc:6.4.0.
> 
> Sorry? gcc:6.4.0 compiles just fine. I cannot rebuild gcc:4.8.5 nor
> gcc:4.7.4 using gcc:6.4.0. Which build logs do you need?

Ah, got it. gcc:4.8.5 logs should be fine.

[Comment 10 Gerrit Kühn 2018-08-13 07:24:57 UTC]

Created attachment 543230 [details]
build.log for gcc-4.8.5

Build log as requested.

[Comment 11 Gerrit Kühn 2018-08-13 08:09:30 UTC]

Created attachment 543236 [details]
build.log for gcc-4.8.5 using gcc-6.4.0

Another build log with different errors, this time using gcc-6.4.0 as compiler (the other one used gcc-5.4.0).

[Comment 12 Sergei Trofimovich (RETIRED) 2018-10-27 21:23:49 UTC]

~arch versions of all gcc slots should compile against glibc-2.28 now.