On 12.10.2010 18:16, Cyril Brulebois wrote: > Source: stockfish > Version: 1.9.1-1 > Severity: serious > Justification: FTBFS > User: debian-sp...@lists.debian.org > Usertags: sparc
It does build nice on sperger(sparc) and merulo(ia64) in a sid chroot. This is an gcc 4.4.4. Even with profiling switched on everything worked out well. I am not so experienced in these porting issues, what do you think is the right thing to do: - File a bug against gcc?!?: I could not test experimental on sperger, no chroot there, and there is a gcc 4.5.1 in experimental. - switch profiling off: nobody will need any stockfish on sparc or ia64 hardware, and if someone does, a non-profile build will do. I tend to the second possibility, but I am curious, if you have any advice for me. Thanks in advance, Oliver -- snip end of merulos log-- dh_usrlocal -O--sourcedirectory=src dh_link -O--sourcedirectory=src dh_compress -O--sourcedirectory=src dh_fixperms -O--sourcedirectory=src dh_strip -O--sourcedirectory=src dh_makeshlibs -O--sourcedirectory=src dh_shlibdeps -O--sourcedirectory=src dpkg-shlibdeps: warning: dependency on libunwind.so.7 could be avoided if "debian/stockfish/usr/games/stockfish" were not uselessly linked against it (they use none of its symbols). dh_installdeb -O--sourcedirectory=src dh_gencontrol -O--sourcedirectory=src dh_md5sums -O--sourcedirectory=src dh_builddeb -O--sourcedirectory=src dpkg-deb: building package `stockfish' in `../stockfish_1.9.1-1_ia64.deb'. dpkg-genchanges >../stockfish_1.9.1-1_ia64.changes dpkg-genchanges: including full source code in upload dpkg-source --after-build stockfish-1.9.1 dpkg-buildpackage: full upload (original source is included) (sid)ok...@merulo:~/stockfish-1.9.1$ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
