configure: Treat warnings as errors in check_yasm()
yasm generates a warning instead of an error when "CPU amdnop" is not supported, so the check always succeeds. HAVE_CPUNOP as true when the available yasm version doesn't support amdnop doesn't make sense. Check http://fate.ffmpeg.org/log.cgi?time=20120901143315&log=compile&slot=x86_64-archlinux-gcc-oldyasm to see the amount of warnings it generates. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
This commit is contained in:
parent
19a71dbcb9
commit
c112b6b68f
2
configure
vendored
2
configure
vendored
@ -747,7 +747,7 @@ check_yasm(){
|
|||||||
echo "$1" > $TMPS
|
echo "$1" > $TMPS
|
||||||
log_file $TMPS
|
log_file $TMPS
|
||||||
shift 1
|
shift 1
|
||||||
check_cmd $yasmexe $YASMFLAGS "$@" -o $TMPO $TMPS
|
check_cmd $yasmexe $YASMFLAGS -Werror "$@" -o $TMPO $TMPS
|
||||||
}
|
}
|
||||||
|
|
||||||
ld_o(){
|
ld_o(){
|
||||||
|
Loading…
x
Reference in New Issue
Block a user