[email protected] said: > I can relate to that problem. Though, did you just try using it with > rumprun-xen?
No, I assumed that if gcc -m32 can't create a host executable then it no work. I'll give it another go. > IIRC building rumpuser-baremetal with -m32 just worked, while trying to > build a host executable with -m32 got me into some package jungle with > no way out. > > > I have however installed an i386 chroot and built it there. Have now > > synced the x86-32 specific bits with the namespace changes, it builds and > > runs hello, world fine. > > > > These changes have been pushed to my Github branch. > > great, thanks! > > I assume this was the last bit of the cleanup. I don't think there's > anything very controversial in there, so depending on how you want to > work, we can merge it to rumprun-xen master and then you continue to > work out the details with other projects. Or you can first work out all > the details, and then we merge. The former route might be the quicker > way to get your project working on rumprun-xen master, the latter route > might be marginally less back-and-forth work. I think I'd prefer the former. "Working out all the details" has a tendency to turn in "large chunk of work". :-) To get the patches merged upstream they need to be rebased against the upstream mini-os, and also I guess in that case I should do a "full" rename of the namespace including macros and other potentially public APIs. The patch set at it stands only renames the bare minimum needed for by rumprun-xen. So, I'll make you a pull request for what we have now and continue the work I want to do while communicating with the various projects about upstreaming the minios changes. Martin ------------------------------------------------------------------------------ _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
