Summary: | sys-block/unieject uses -Werror during configure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | flameeyes |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/var/tmp/portage/sys-block/unieject-6/work/unieject-6/config.log
/var/log/portage/build/sys-block/unieject-6:20100906-064947.log |
Description
Justin Lecher (RETIRED)
2010-09-06 06:47:50 UTC
Created attachment 246224 [details]
/var/tmp/portage/sys-block/unieject-6/work/unieject-6/config.log
config.log
Created attachment 246228 [details]
/var/log/portage/build/sys-block/unieject-6:20100906-064947.log
build.log
Diego, is there a way to switch that off? No, not really.. -Wimplicit-function-declaration and autoconf don't get along together. a) -Werror is the only way to catch if the attributes work at all as often enough they just emit warnings; b) AC_CHECK_LIB/AC_SEARCH_LIB will also fail with -Werror=implicit-function-declaration so if the two are combined will be a problem. But really it would be simpler if somebody picked up unieject upstream at this point, I haven't worked on it for way too long. I am using that flag to catch flags mixtures as a C-only FLAG. Which other would you suggest? http://blog.flameeyes.eu/2008/08/06/flags-and-flags I have some code out there to implement that kind of testing in non-disruptive ways. (In reply to comment #6) > http://blog.flameeyes.eu/2008/08/06/flags-and-flags > > I have some code out there to implement that kind of testing in non-disruptive > ways. > Oh I missed that one. I only knew your other with the flagcheck.h. Thanks again. |