Steve Langasek <[EMAIL PROTECTED]> writes: > 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.
Interesting. It looks like prctl --unaligned=signal fakeroot debian/rules binary still works in the merulo unstable chroot. >> - 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. Certainly, but in this case, there's no reason that guile-1.6-libs *should* be a problem. If I were to add it to the Build-Conflicts, that would just be speculative. Of course if nothing else turns up, I suppose we might be left with a speculative buildd run as our only option, but I was hoping we might be able to identify the problem more directly. Also, above, I was just wondering about the likelihood that guile-1.6-libs might be a problem, even though it shouldn't be. Thanks for the help. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
