Watching Arm failures

Information Source:

[http://buildd.debian.org/~jeroen/status/architecture.php?a=arm Arm buildd]

Feel free to:

gcc4 ICEs

unclassified ICE's

These need proper bugreports generating and filing upstream. Comparing against cvs-snapshot on an unstable system if you can.

{{{pattern.c: In function 'piece_to_pattern_distance': pattern.c:506: fatal error: internal consistency failure compilation terminated.}}}

{{{ugsc.c: In function 'phaser1set': ugsc.c:334: fatal error: internal consistency failure compilation terminated.}}}

{{{cc -g -Wall -O2 -fPIC -rdynamic -Wl,-export-dynamic -L. main.o -lruby1.9 -lpthread -ldl -lcrypt -lm -o ruby1.9 make[2]: Leaving directory `/build/buildd/ruby1.9-1.9.0+20050921' lib/fileutils.rb:449: [BUG] Segmentation fault ruby 1.9.0 (2005-09-21)[arm-linux] }}}

bumprace.h:10:22: error: "$" may not appear in macro parameter list

EABI stuff leaking through gcc?

Normal issues

missing closure support in libffi

This causes libffi-using programs to blow up with [http://buildd.debian.org/~jeroen/status/package.php?p=ctypes&a=arm#fail-arm obscure errors] when they try to declare an "ffi_closure" object.

move to failed - bugs filed

depwait

needs retrying

needs urgent research - regressions

needs research - never worked

java

This is pretty bad, since db* want java. gcj-4.0 (as opposed to gcj-3.3 and gcj-3.4) does work fine on ARM, but gij-4.0 does not. See #337263. Using a different VM such as sablevm might be a solution here.

== yacc==

There is several packages failing to build because /usr/bin/yacc is missing - builddd setup issue

not-for-us

These packages are not for arch=arm so are not expected to build. They still appear on the buildd status pages as failures.

fixed/past issues