On Thu, May 11, 2006 at 06:51:15PM -0700, Rob Browning wrote: > Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> > So my question from Monday is still there. Perhaps following the > > suggestion in the bug log will solve the problem? > Here's where things stand: > - I tried building the package in merulo's unstable chroot. That > worked fine. Since the chroot doesn't have slib installed, and > neither did the buildd (according to the log), slib's not likely > to be the problem. A data point that might be relevant here is that builds on merulo are run using prctl --unaligned=signal, whereas the default on hppa and ia64 is to not signal on unaligned traps. I'm not sure how this would cause the guile-1.6 failure, but it *is* a difference to keep in mind. > - The other suggestion was to make sure guile-1.6-libs isn't > installed. If the buildd starts from scratch for each package > (does it?), then that guile-1.6-libs couldn't be the problem. If > the buildd doesn't start from scratch, then it would seem a little > surprising if the problem only occurs on ia64. If there are any packages that you *require* to not be installed for the build, you need to add a Build-Conflict on them anyway even if you think that the buildd won't have those packages installed. It's not *likely* to be installed, but the build log also won't tell you this information normally unless something in your package's build gives a visual indicator of this itself. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
