Bug 81712 - gcc does not compile when using glib 2.26 (everything works fine with 2.25)
Summary: gcc does not compile when using glib 2.26 (everything works fine with 2.25)
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: other (show other bugs)
Version: 7.1.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
: 81775 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-08-04 07:21 UTC by Igor Chubin
Modified: 2017-11-19 11:41 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work: 7.1.1
Known to fail: 7.1.0
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Chubin 2017-08-04 07:21:02 UTC 
The compilation process stops with the following error message:


./md-unwind-support.h: In function 'x86_64_fallback_frame_state':
./md-unwind-support.h:65:47: error: dereferencing pointer to incomplete type 'struct ucontext'
       sc = (struct sigcontext *) (void *) &uc_->uc_mcontext;
                                               ^~
make[3]: Leaving directory `/disk2/build/gcc-7.1.0-build/x86_64-pc-linux-gnu/libgcc'
make[3]: *** [unwind-dw2.o] Error 1
make[2]: Leaving directory `/disk2/build/gcc-7.1.0-build'
make[2]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/disk2/build/gcc-7.1.0-build'
make[1]: *** [all] Error 2
Comment 1 Andrew Pinski 2017-08-04 07:27:16 UTC 
This might already be fixed for 7.2.0.
Comment 2 Igor Chubin 2017-08-04 07:29:40 UTC 
Perfect. I'll try to build gcc-7.2-RC-20170802
Comment 3 Igor Chubin 2017-08-04 07:54:11 UTC 
Perfect. I'll try to build gcc-7.2-RC-20170802
Comment 4 Richard Biener 2017-08-04 08:06:32 UTC 
Yes, I think that part works now.
Comment 5 Andrew Pinski 2017-08-08 18:50:41 UTC 
*** Bug 81775 has been marked as a duplicate of this bug. ***
Comment 6 Jonathan Wakely 2017-10-19 22:32:39 UTC 
Fixed by r249731 on trunk and r249956 on gcc-7-branch
Comment 7 Jan Smets 2017-11-07 13:02:30 UTC 
Any chance of the fix being backported to the 6 branch, for the 6.5 release?
Comment 8 Mikael Pettersson 2017-11-19 11:41:20 UTC 
The fix was backported to gcc-6-branch in r249957 and to gcc-5-branch in r249958.  So it's included in gcc-5.5.0 and will be included in gcc-6.5.0.