SPARC build failure of texlive-bin

2007-11-15 Thread Norbert Preining
Dear all! The last build of texlive-bin didn't succeed, but it seems that the build process was somehow interrupted or something else is strange: dh_strip dh_shlibdeps -L libkpathsea4 -l debian/libkpathsea4/usr/lib make: *** [binary-arch] Terminated Build killed with signal 15 after 150

Re: SPARC build failure of texlive-bin

2007-11-15 Thread Frank Lichtenheld
On Thu, Nov 15, 2007 at 12:07:41PM +0100, Norbert Preining wrote: On Do, 15 Nov 2007, Frank Lichtenheld wrote: Should work once the fixed kernels that seem now available are reaching the buildds. Do I have to ping the autobuilder in some way, or will this be tried without my interference?

Re: SPARC build failure of texlive-bin

2007-11-15 Thread Norbert Preining
On Do, 15 Nov 2007, Luk Claes wrote: This means that dh_shlibdeps was running for 150 minutes without sending any output to the build log. To make sure buildds won't wait forever Yes, that I did understand, but why? There were only a few patches added that affect the compilation process:

Re: SPARC build failure of texlive-bin

2007-11-15 Thread Luk Claes
Norbert Preining wrote: Dear all! The last build of texlive-bin didn't succeed, but it seems that the build process was somehow interrupted or something else is strange: dh_strip dh_shlibdeps -L libkpathsea4 -l debian/libkpathsea4/usr/lib make: *** [binary-arch] Terminated Build

Re: SPARC build failure of texlive-bin

2007-11-15 Thread Frank Lichtenheld
On Thu, Nov 15, 2007 at 11:23:38AM +0100, Norbert Preining wrote: The last build of texlive-bin didn't succeed, but it seems that the build process was somehow interrupted or something else is strange: dh_strip dh_shlibdeps -L libkpathsea4 -l debian/libkpathsea4/usr/lib make: ***

Re: SPARC build failure of texlive-bin

2007-11-15 Thread Norbert Preining
Dear Frank! On Do, 15 Nov 2007, Frank Lichtenheld wrote: The kernel problems that plagued sparc for the last few months would be the likely suspect for that since they caused looping, unkillable dpkg-query processes, most often from dpkg-shlibdeps. Ah, thanks, that explains the strange