Copying this to the appropriate bug... On 01/08/10 11:38, Adam D. Barratt wrote: > On Fri, July 30, 2010 19:02, Felipe Sateler wrote: >> On 30/07/10 13:25, Adam D. Barratt wrote: >>> - ardour: FTBFS on sparc (#590863) >>> - csound: FTBFS on hppa (#590948) >>> - slv2: FTBFS on hppa (#590976) >> >> All these three look like problems with the buildd host/toolchain. >> CSound hangs in a doxygen call that has not been modified since the -1 >> upload. Trying to build that same documentation in paer gives me >> segmentation faults in doxygen in different stages almost every time (I >> managed to build it after a few retries). > > Of the four tries on the buildds, csound hung in doxygen twice and during > the source build twice, afaics. That and the fact that it needed several > tries on paer suggest that even if we it managed to build after another > attempt or three, the next binNMU or sourceful upload may well have the > same problem(s). Indeed. How do you suggest working through this? Facts: 1. The build hangs unpredictably on a doxygen call. 2. The doxygen call is in build-indep (so it is not strictly necessary for binary only builds, but gets executed anyway). I can move the doxygen call away from there into binary-indep, but that feels like a hack to me. I have been trying to build the doxygen documentation a few times, and it looks like either doxygen is doing something wrong with pthread mutex calls or the hppa kernel/libc are doing something wrong with the calls doxygen makes. I'm getting some assertion failures now too: doxygen: pthread_mutex_lock.c:62: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. All hangs and segmentation faults seem to happen inside synchronization calls (futex calls). I have not been able to reproduce the hang in the Generating docs for compound ... stage. > >> The paer sid chroot does not >> have the necessary build deps, so I can't binNMU it myself. > > You can, you just need to request that the build-deps be installed. Not necessary, since the faulty command (doxygen) is already installed and I do not plan on working around this bug by manually uploading a package that will have the same problem again. -- Saludos, Felipe Sateler
Attachment:
signature.asc
Description: OpenPGP digital signature