On May 30, 2012, at 16:10, Jeremy Huddleston wrote:

> In my case, config.log shows that the check is behaving correctly:
> 
> configure:12684: checking whether to use MMX intrinsics
> configure:12709: /opt/local/libexec/llvm-3.0/libexec/scan-build/ccc-analyzer 
> -c -mmmx -Winline -O0 -g3 -pipe  -fdiagnostics-show-category=name -Wall 
> -fno-strict-aliasing -fvisibility=hidden 
> -I/Users/jeremy/src/freedesktop/jhbuild/build/include 
> -I/Users/jeremy/src/freedesktop/jhbuild/external/build/include conftest.c >&5
> fatal error: error in backend: Invalid operand for inline asm constraint 'K'!
> configure:12709: $? = 1
> configure: failed program was:
> …
> configure:12735: result: no
> 
> but Ryan's config.log shows that it is not catching it for him:
> configure:12648: checking whether to use MMX intrinsics
> configure:12673: /opt/local/bin/clang-mp-3.0 -c -mmmx -Winline -pipe -O2 
> -arch x86_64 -Wall -fno-strict-aliasing -fvisibility=hidden 
> -I/opt/local/include conftest.c >&5
> configure:12673: $? = 0
> configure:12699: result: yes
> 
> so maybe there are issues with the CFLAGS there, and the test for the bug 
> needs to be improved...

What is /opt/local/libexec/llvm-3.0/libexec/scan-build/ccc-analyzer and why is 
your build using that instead of /opt/local/bin/clang-mp-3.0? If I set 
configure.cc to that then it builds for me too.

_______________________________________________
Pixman mailing list
Pixman@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/pixman

Reply via email to