Hello, 2011/10/7 Thorsten Glaser <[email protected]>:
> Could you please try to find out exactly _why_ (or at least _where_) > this segfaults, as I’m not in the possession of access to an armhf > box – as far as I can see, the programme is valid C, and if this > segfaults on armhf, dietlibc is as broken there as on hppa and > should indeed FTBFS due to failing this test. (Please do also try > whether this segfaults with eglibc.) FWIW, both versions with armhf fixes build fine on my armhf box: Version: 0.33~cvs20110710-2 bin-'arm'/diet -v -Os gcc -nostdinc -static -o ttt debian/test/tc523086.c gcc -nostdlib -static -L/home/zumbi/dietlibc-0.33~cvs20110710/bin-arm /home/zumbi/dietlibc-0.33~cvs20110710/bin-arm/start.o -nostdinc -static -o ttt debian/test/tc523086.c -isystem /home/zumbi/dietlibc-0.33~cvs20110710/include -D__dietlibc__ -Os -fomit-frame-pointer /home/zumbi/dietlibc-0.33~cvs20110710/bin-arm/dietlibc.a -lgcc /home/zumbi/dietlibc-0.33~cvs20110710/bin-arm/dietlibc.a /home/zumbi/dietlibc-0.33~cvs20110710/bin-arm/dietlibc.a(vprintf.o): In function `vprintf': vprintf.c:(.text+0x2c): warning: warning: the printf functions add several kilobytes of bloat. ./ttt ok: <ad> Version: 0.33~cvs20110918-3 bin-'arm'/diet -v -Os gcc -nostdinc -static -o ttt debian/test/tc523086.c gcc -nostdlib -static -L/home/zumbi/dietlibc-0.33~cvs20110918/bin-arm /home/zumbi/dietlibc-0.33~cvs20110918/bin-arm/start.o -nostdinc -static -o ttt debian/test/tc523086.c -isystem /home/zumbi/dietlibc-0.33~cvs20110918/include -D__dietlibc__ -Os -fomit-frame-pointer /home/zumbi/dietlibc-0.33~cvs20110918/bin-arm/dietlibc.a -lgcc /home/zumbi/dietlibc-0.33~cvs20110918/bin-arm/dietlibc.a /home/zumbi/dietlibc-0.33~cvs20110918/bin-arm/dietlibc.a(vprintf.o): In function `vprintf': vprintf.c:(.text+0x2c): warning: warning: the printf functions add several kilobytes of bloat. ./ttt ok: <ad> Not sure if it can be an armhf buildd issue. Cheers, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
