On Mon, 19 Aug 2024 at 17:55:34 +0200, John Paul Adrian Glaubitz wrote:
> On Mon, 2024-08-19 at 16:46 +0100, Simon McVittie wrote:
> > - is there any other container/chroot/confinement going on, or is it
> > sbuild + schroot running on a real machine?
>
> It's sbuild + schroot on a real machine running unstable.
How was the sbuild chroot created? (With a simple invocation of
sbuild-createchroot from 0.85.10, or with any special configuration, or
with some different tool?)
I can't immediately tell from the gcc build log you linked[1] whether
this is a directory on disk, or a tarball that gets unpacked onto a
scratch filesystem, or what; can you clarify?
If you have access to the machine and can `cd /path/to/chroot; find /dev -ls`
in the chroot base directory (or a temporarily unpacked copy of the tarball
if it's a tarball), *without* schroot's setup scripts having run on it,
that would probably also be useful information.
Thanks,
smcv
[1]
https://buildd.debian.org/status/fetch.php?pkg=gcc-14&arch=ppc64&ver=14.2.0-3&stamp=1724003978&raw=0
