debian mipsel build issues about castxml

[bradking]

Thanks. What is the output of

$ gcc -c test/input/GNU-float128.c ; echo $?

on this architecture?

[smr99]

Brad: did not run your test, but I thought I'd mention that Debian has at least 7 architectures showing the same failure: https://buildd.debian.org/status/package.php?p=castxml&suite=unstable

In each case, all six "float128" tests fail. Is there a way you can condition the test on the existence of the __float128 type?

[bradking]

@smr99 Yes, I've already drafted changes to make the float128 tests conditional based on the results of running gcc on the corresponding source file. That's why I want to verify that gcc fails as expected to build the test source file, but I do not have access to the architecture.

[smr99]

@bradking: I ran your command on arm64 and mipsel. Both yielded the same output (I expect all will, since they use the same gcc):

(sid_arm64-dchroot)smr@asachi:~/castxml-0.1+git20150630$ gcc -c test/input/GNU-float128.c ; echo $?
test/input/GNU-float128.c:1:1: error: unknown type name '__float128'
__float128 start(__float128);
^
test/input/GNU-float128.c:1:1: warning: parameter names (without types) in function declaration
1

[bradking]

@smr99: Thanks, that is what I was hoping it would do. I've pushed commit d30d102 to enable the float128 tests only if gcc has the __float128 type and can compile the test source file.