Re: cross compilation tool versions
On Mon, Mar 20, 2000 at 01:03:11PM -0500, Roland McGrath wrote:
> Personally, I use the same cross-compilation environment for oskit, libc,
> hurd, and both microkernels, just to keep it uniform and simple for myself.
> But if you are just compiling oskit and/or the microkernel(s), then I'd go
> with simple native tools instead. (In the case of the oskit, building
> native on linux or freebsd also gives you the "oskit-on-unix" support,
> which is not of any use with mach, but is nice for playing with little
> oskit things in general.)
>
> Note that there is a debian binary package for (linux) x86 of the last
> oskit snapshot (though I don't know what compiler Ed built it with). The
> oskit is a big old beast to compile (it's your usual painless GNUish
> configure/make deal, it's just a huge mother), so you might not want to
> deal with it unless you really want to hack on the oskit and want -g
> symbols in it and so forth. Since all the drivers are in the oskit,
> oskit-mach is pretty small and quick to compile once you have the oskit
> installed.
I wonder if it's possible to include only selected drivers from oskit into the
oskit-mach kernel. If you get the debian oskit package it seems to have all
the drivers compiled in. Would I have to recompile the oskit sources with
selected options for that?
Igor
Reply to: