mig cross-toolchain
Hello Helmut,
We now have the cross-mig packages in the archive, and I have uploaded
gnumach & hurd to build-depend mig-for-host instead of mig.
There are however two things that may pose problem:
- mig-for-host:hurd-i386 is multi-arch: same and depends on
mig-i686-gnu:
Package: mig-for-host
Source: mig
Architecture: hurd-i386
Depends: mig-i686-gnu
Multi-Arch: same
[...]
and mig-i686-gnu:amd64 doesn't have a multi-arch field
(explictly removed in debian/rules, I don't remember why):
Package: mig-i686-gnu
Source: mig
Architecture: amd64
Depends: libc6 (>= 2.14), libfl2 (>= 2.5.33)
[...]
Don't we want to make mig-i686-gnu:amd64 multi-arch:foreign so
that it can fill the dependency of mig-for-host and provide a
/usr/bin/i686-gnu-mig that can actually be executed? When I keep it
multi-arch:foreign things seem to be working fine.
- When I add_automatic mig, once the mig source package is cross-built
automatically, the result (mig:hurd-i386 mig-for-host:hurd-i386
mig-i686-gnu:hurd-i386) replaces completely the mig_1 build
(mig-i686-gnu:amd64) which gets moved to archive/:
./archive/mig_1
./archive/mig_1/mig-i686-gnu_1.8+git20200618-2_amd64.deb
./pool/main/m/mig
./pool/main/m/mig/mig-for-host_1.8+git20200618-2_hurd-i386.deb
./pool/main/m/mig/mig_1.8+git20200618-2_hurd-i386.deb
./pool/main/m/mig/mig-i686-gnu_1.8+git20200618-2_hurd-i386.deb
I guess it's the reboostrap automatic build that does not support
merging with previous builds for another architecture?
Samuel
Reply to: