[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: globus-net-manager FTBFS during python 3.10 transition

On 5/16/22 03:28, John Paul Adrian Glaubitz wrote:
> Hi Matthias!
> On 5/16/22 10:24, Mattias Ellert wrote:
>> I have noticed that in addition to m68k and sh4, the builds also fail
>> in the same way on the hppa host known as pasta, but when given back
>> and run on a different hppa host they succeed.
>> E.g.
>> https://buildd.debian.org/status/logs.php?pkg=globus-common&arch=hppa
>> One failure on pasta - give back succeded on pacific
>> https://buildd.debian.org/status/logs.php?pkg=globus-gass-transfer&arch=hppa
>> Two failures on pasta - third attempt on physik succeeded
>> Is this related?
> pasta is using a similar setup like m68k and sh4.
> The underlying bug is an issue with glibc and ext4 [1] and can be resolved
> by switching the buildroot to btrfs. I have verified that this fixes the
> issue.

I've generally found qemu's application emulation to be MUCH more brittle than
its system emulation, so I usually create little system emulation versions to
native compile under instead. (Currently
https://landley.net/toybox/downloads/binaries/mkroot/latest/ ala
https://landley.net/toybox/faq.html#mkroot previously
https://landley.net/aboriginal/downloads/binaries/ ala
https://landley.net/aboriginal/about.html .)

QEMU's sh4 system emulation only has 64 megs ram, but you can add as much swap
space as you like and the compiler's been happy with it so far. (Even when it
gets a little thrashy, it stays in the host's page cache so it's all
memory-to-memory copying. I have a todo item to map some more memory into the
virtual board and kernel, but both sides involve a lot of digging.) The m68k
board I'm using has 256 megs ram, that's generally enough for a -j1 build. (Or
even -j3 with distcc calling out to the cross compiler running on the host's
loopback instead of running in the emulator.) I haven't tried to get an hppa
system working yet because musl doesn't support it.

That said, I've never figured out how to do a fully from-source debootstrap.
(I.E. build a Debian root filesystem from source under a Linux From Scratch
system and use that to populate a binary package repository.) Everything always
assumes "fetch binary packages from an existing repository to populate a
chroot", which means the architecture and libc combination has to already exist.

I'd really like to try doing a musl version of debian, but every documented
process I can find starts with "have this script wget a bunch of glibc binaries
off a server". Is there documentation on actually doing it entirely from source


Reply to: