Bug#672820: failed attempt to build xmms2, blocking libcdio transition.
Hello Debian/BSD hackers, I've recently upload an new version of xmms2 to fix an FTBS[1] and help a libcdio transition[2]. But the build failed on both kfreebsd buildd (fano[3] and finzi[4]) at very different stage of compilation, but in both case waf or gcc hang, and the build was killed after some time. Is there anything I should know/do about this problem on the kfreebsd port? Thanks [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676100 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672820 [3] https://buildd.debian.org/status/fetch.php?pkg=xmms2arch=kfreebsd-amd64ver=0.8%2Bdfsg-3stamp=1340024041 [4] https://buildd.debian.org/status/fetch.php?pkg=xmms2arch=kfreebsd-i386ver=0.8%2Bdfsg-3stamp=1340032320 -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672820: failed attempt to build xmms2, blocking libcdio transition.
Hi, On 18/06/12 20:01, Rémi Vanicat wrote: [...] in both case waf or gcc hang, and the build was killed after some time. I think there is a problem affecting Python threads on kfreebsd-* currently, perhaps a bug in our glibc, and this has been seen sometimes when building other packages that use waf: samba4, guitarix. It seems random, so in some cases they build okay after being given back to the buildds for another attempt. (Looks like xmms2 just built successfully after a giveback). The cause of this may be difficult to track down; it's not easy to reproduce it on demand. Sorry for the inconvenience! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
