Hello, Helmut Grohne, le ven. 18 févr. 2022 14:13:09 +0100, a ecrit: > On Fri, Feb 18, 2022 at 12:45:57PM +0100, Guillem Jover wrote: > > Just to spell out, what might perhaps be obvious here, but I think > > they key is that MIG is "kernel independent", so it provides an > > interface which is none-<cpu> which means it can be used on any-<cpu> > > to target hurd-<any>. Perhaps this should be mentioned in the packages > > description, because otherwise I agree it seems a bit confusing? > > Thank you. In that case, I think it shouldn't be mig-x86-64-linux-gnu > nor mig-x86-64-gnu nor mig-x86-64-kfreebsd-gnu, but simply mig-x86-64 as > that's what it is specific to.
Mmm, it still targets hurd-<any> explicitly, so I'd say it should still be called mig-x86-64-gnu. What I'm wondering is why we added -linux/-kfreebsd since here they are host, not target. The package name is supposed to designated the target doesn't it? I'm actually now unsure what "mig-for-host" was supposed to mean. AIUI we'd want it to pull a native-for-host binary that targets the architecture equivalent on the hurd port. E.g. on linux-amd64 it'd pull a linux-amd64 x86-64-gnu-mig binary. Currently gnumach is fine with this checking for i686-gnu-mig... i686-linux-gnu-mig but that's still relatively bogus. Samuel
