On 30/12/14 17:51, Justin Cormack wrote: >> Regardless of where the code resides, I'm not sure we can use autoconf >> for selecting the build target. For one, we can't run autoconf before >> we have a target env available, which is very late in the build process >> for non-hosted envs (xen, baremetal, ...) > > Yes it is not clear, it depends on how the process is staged, > configure would have to be run quite late.
And for two, autoconf is really meant to probe differences between platforms. We'd just be probing the features provided by rumprun, and I sure hope we know what that env provides even without running probes. > Maybe we should spin out a rumpuser git repo, try to sort out these > issues and the ABI update and then merge something back into NetBSD > once it has settled down. Whats in NetBSD is fine for the purposes it > needs to be in tree for (tests), and can probably just sit unchanged > for a few months. Sure. In-tree NetBSD has different requirements from not-in-tree NetBSD, so there's no real requirement to keep the two the same. The only thing that must not change is the hypercall interface, but that's more or less a given anyway. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
