Summary: | usbredir-0.5 fails to build due to -Werror in configure.ac | ||
---|---|---|---|
Product: | Spice | Reporter: | Samuli Suominen <ssuominen> |
Component: | usbredir | Assignee: | Hans de Goede <jwrdegoede> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Samuli Suominen
2012-09-07 14:27:26 UTC
Please include configure option like ./configure --enable-werror which you can use... or vice versa, what ever Thank you, Samuli (In reply to comment #1) > Please include configure option like ./configure --enable-werror which you can > use... or vice versa, what ever > > Thank you, > Samuli configure only sets a set of default CFLAGS if you don't set any CFLAGS yourself before calling configure, this is done to make sure that any warnings are caught during day to day development (the warning you're seeing seems to be specific to your gcc / glibc versions). Doing: export CFLAGS="-g -O2 -Wall" ./configure ... Should fix your issue. p.s. I've fixed the (harmless) warning in upstream git master. (In reply to comment #2) > (In reply to comment #1) > > Please include configure option like ./configure --enable-werror which you can > > use... or vice versa, what ever > > > > Thank you, > > Samuli > > configure only sets a set of default CFLAGS if you don't set any CFLAGS > yourself before calling configure, this > is done to make sure that any warnings are caught during day to day development > (the warning you're seeing seems to be specific to your gcc / glibc versions). > > Doing: > export CFLAGS="-g -O2 -Wall" > ./configure ... > > Should fix your issue. I find this bad and unstandard behavior. I cannot guarantee every user has CFLAGS set, having them unset is valid configuration too. However I've worked this around by always setting CFLAGS to -Wno-error before it hits configure phase in Gentoo's package (ebuild) with a reference to this bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.