On Monday, April 21, 2025 2:46:27 a.m. Central Daylight Saving Time Johannes Schauer Marin Rodrigues wrote:
> > I also can't figure out how to examine the chroot after a failure: > > using "-- > > purge=successful" doesn't work with unshare. > > I usually use --anything-failed-commands=%s which gives you a shell that > you can use to investigate the build independent of the chroot backend. That was the hint I needed, many thanks. I was able to confirm that the cmake configuration was identical when using the unshare backend. So I started looking at the sources. I have managed to solve this by adding an #include in one of the files. To me, this looks like a true bug in ITK so I am completely baffled by why it works in a regular build -- or with the schroot backend of sbuild. I also confirmed that the previously uploaded version of ITK does build with both schroot and unshare backends of sbuild. I looked at the diffs and none of the changes looked suspicious -- indeed the code that was failing wasn't even changed. So I'll take the win of a successful build, but I have no idea what the root cause was. As ever - very grateful for the suggestions received here! Regards, -Steve
signature.asc
Description: This is a digitally signed message part.
