Summary: | sys-libs/glibc-2.28 with sys-devel/gcc-4.9.4 - n file included from pthread_mutex_getprioceiling.c:21: pthread_mutex_getprioceiling.c: In function 'pthread_mutex_getprioceiling': ../include/atomic.h:672:4: error: read-only variable '__atg100_val' used as | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hans F. Nordhaug <hansfn> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | joakim.tjernlund |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Hans F. Nordhaug
2019-03-29 11:31:36 UTC
A typo: "if the problematic commit has been backported to 2.27" => "if the problematic commit has been backported to 2.28". I think you still can build glibc with new gcc and have old gcc installed alongside and use it for other tools. Note: <gcc-6 is masked and is not supported as a system compiler. Having said that we can apply patches to gcc or glibc if those are safe. Please post full build.log and 'emerge --info'. Maybe that will shed some light as well. It turned out to be a misconception that we needed to build glibc with GCC 4.9.4 to make our (old) applications run. It was enough to compile a selection of other libraries with GCC 4.9.4. In other words, you can close this issue. Sorry about wasting your time. Other people with this issue (if any) at least has this report as starting point and a work-around. No problem. *** Bug 697554 has been marked as a duplicate of this bug. *** |