Alan Hourihane dixit: >Thanks Thorsten that'll help
np >I'll battle on with my TT to get Linux >running and try myself soon. That will also help! Here we are: FAIL: libffi.call/err_bad_abi.c -O0 -W -Wall execution test FAIL: libffi.call/nested_struct2.c -O0 -W -Wall execution test FAIL: libffi.call/return_ldl.c -O0 -W -Wall execution test FAIL: libffi.call/cls_longdouble.c -O2 output pattern test, is 1 2 3 4 5 6 7 8: 36 FAIL: libffi.call/err_bad_abi.c -O2 execution test FAIL: libffi.call/float4.c -O2 execution test FAIL: libffi.call/float_va.c -O2 output pattern test, is 0: 2.0 : total: 2.0 FAIL: libffi.call/nested_struct2.c -O2 execution test FAIL: libffi.call/return_dbl.c -O2 execution test FAIL: libffi.call/return_dbl1.c -O2 execution test FAIL: libffi.call/return_dbl2.c -O2 execution test FAIL: libffi.call/return_fl.c -O2 execution test FAIL: libffi.call/return_fl1.c -O2 execution test FAIL: libffi.call/return_fl2.c -O2 execution test FAIL: libffi.call/return_fl3.c -O2 execution test FAIL: libffi.call/return_ldl.c -O2 execution test FAIL: libffi.call/return_sc.c -O2 execution test FAIL: libffi.call/cls_longdouble.c -O3 output pattern test, is 1 2 3 4 5 6 7 8: 36 FAIL: libffi.call/err_bad_abi.c -O3 execution test FAIL: libffi.call/float4.c -O3 execution test FAIL: libffi.call/float_va.c -O3 output pattern test, is 0: 2.0 : total: 2.0 FAIL: libffi.call/nested_struct2.c -O3 execution test FAIL: libffi.call/return_dbl.c -O3 execution test FAIL: libffi.call/return_dbl1.c -O3 execution test FAIL: libffi.call/return_dbl2.c -O3 execution test FAIL: libffi.call/return_fl.c -O3 execution test FAIL: libffi.call/return_fl1.c -O3 execution test FAIL: libffi.call/return_fl2.c -O3 execution test FAIL: libffi.call/return_fl3.c -O3 execution test FAIL: libffi.call/return_ldl.c -O3 execution test FAIL: libffi.call/return_sc.c -O3 execution test FAIL: libffi.call/cls_longdouble.c -Os output pattern test, is 1 2 3 4 5 6 7 8: 36 FAIL: libffi.call/err_bad_abi.c -Os execution test FAIL: libffi.call/float4.c -Os execution test FAIL: libffi.call/float_va.c -Os output pattern test, is 0: 2.0 : total: 2.0 FAIL: libffi.call/nested_struct2.c -Os execution test FAIL: libffi.call/return_dbl.c -Os execution test FAIL: libffi.call/return_dbl1.c -Os execution test FAIL: libffi.call/return_dbl2.c -Os execution test FAIL: libffi.call/return_fl.c -Os execution test FAIL: libffi.call/return_fl1.c -Os execution test FAIL: libffi.call/return_fl2.c -Os execution test FAIL: libffi.call/return_fl3.c -Os execution test FAIL: libffi.call/return_ldl.c -Os execution test FAIL: libffi.call/return_sc.c -Os execution test FAIL: libffi.call/cls_longdouble.c -O2 -fomit-frame-pointer output pattern test, is 1 2 3 4 5 6 7 8: 36 FAIL: libffi.call/err_bad_abi.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/float4.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/float_va.c -O2 -fomit-frame-pointer output pattern test, is 0: 2.0 : total: 2.0 FAIL: libffi.call/nested_struct2.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_dbl.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_dbl1.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_dbl2.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_fl.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_fl1.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_fl2.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_fl3.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_ldl.c -O2 -fomit-frame-pointer execution test FAIL: libffi.call/return_sc.c -O2 -fomit-frame-pointer execution test The floating point errors are to be expected (on the emulator), which leaves us with very few others. err_bad_abi.c and nested_struct2.c don’t show a diagnostics in the build log. return_sc.c doesn’t, either (if it isn’t float). So now you can investigate ☺ it’s enough to get build-deps fulfilled, though, and my beloved mc (which sadly uses libglib) works very fine. (On unrelated news, I built the entire stack up to links2, but DirectFB also has run-time issues but compiles fine… OTOH, under X it works. (*) DirectFB/Input: Keyboard 0.9 (directfb.org) (!) [ 1465: 0.000] --> Caught signal 11 (at 0xe7c07b38, invalid address) <-- In case someone is interested. No idea whether DirectFB ever worked on Atari, though.) bye, //mirabilos (who worked 1015-2230 today and aims for 16hrs of sleep now) -- 15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha 15:48⎜<thkoehler:#grml> also warum machen die xorg Jungs eigentlich alles kaputt? :) 15:49⎜<novoid:#grml> thkoehler: weil sie als Kinder nie den gebauten Turm selber umschmeissen durften? -- ~/.Xmodmap wonders… -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
