Summary: | sys-libs/glibc-2.14.1 CFLAGS=-Wextra - configure: error: the compiler must support C cleanup handling | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cody Schafer <jmesmon> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jmesmon, matias.jose.seco |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
glibc-2.14.1-build.log
glibc-2.14.1-config.log |
Description
Cody Schafer
2011-11-29 20:22:02 UTC
Created attachment 294237 [details]
glibc-2.14.1-build.log
i need the config.log from the build dir as an attachment glibc-2.14.1 is building on my ppc32 system with binutils-2.21.1/gcc-4.5.3, so i'll def need to see your config.log to find out what's going on Created attachment 294919 [details]
glibc-2.14.1-config.log
I determined the issue to be the '-Wall -Wextra' I added to my CFLAGS. So probably INVALID unless configure shouldn't fail with them enabled.
yes, using -Werror in global CFLAGS is a bad idea Just a note, it wasn't "-Werror", it was "-Wextra" that's also a bad flag to use globally, but that would break a lot less than -Werror ... there are some configure tests (like the glibc ones) where it has to scrape the *warnings* to see if something is supported because older versions of gcc do not error out when compiled with newer features. it only warns. thus you, by adding extra warnings, cause gcc to emit unrelated warnings and triggered the test to fail. it's a crappy situation to be sure :(. *** Bug 399549 has been marked as a duplicate of this bug. *** |