On 24/07/14 12:56, Ian Jackson wrote: >>> Not without coordinating with code in xen.git. Defining both would be >>> fine IMO. >> >> I'm trying to get rid of the whole "rumpuser-xen" name, because as >> already earlier stated, it refers to the rump kernel hypercall >> implementation, and the whole repo is way beyond that stage now. > > Does that mea the repo is going to change names too ?
Yes, that was the plan, so that things which do the same thing will have similar names (cf. rumpuser-xen vs. rumprun): http://permalink.gmane.org/gmane.comp.rumpkernel.user/283 github handles repo renames extremely well, so if you're worried about the urls, shouldn't be a problem. If you're worried about something else, excellent time to speak up ;) >> I assume xen.git knows it's building Xen stuff, and is only interested >> in if it's building for the rumpapp stack or not. Can we agree to >> define both for now, and phase __RUMPUSER_XEN__ out later? That way, I >> can use the same wrapper on any potential non-Xen platforms. > > Sure, defining both now and phasing __RUMPUSER_XEN__ out is the right > approach. Done. >>>> -exec "$prog" --host=!ARCH!-rumpxen-netbsd CC=!APPTOOLS!/rumpapp-xen-cc >>>> +CC=!APPTOOLS!/rumpapp-xen-cc exec "$prog" --host=!ARCH!-rumpxen-netbsd >>> >>> Um, what is the difference here ? I can't remember why I passed it as >>> an argument but I think I found setting it in the environment wasn't >>> effective. (But perhaps that was in the context of make.) >> >> The difference is it working or not. thttpd with the old configure wrapper: >> >> === snip === >> loading cache ./config.cache >> checking host system type... Invalid configuration >> `amd64-rumpxen-netbsd': machine `amd64-rumpxen' not recognized > > Blimey. Is thttpd's configure autoconf-generated ? I don't > understand why thttpd is doing this when xen.git's configure isn't. Looks like autoconf, but it's a bit prehistoric (2.13). I just added a simple autoconf test to be run by travis CI. The current configure wrapper seems to work against both thttpd and the newly generated test (autoconf 2.69). Travis might even agree once I manage to commit a travis script without typos ... >>>> However, that makes running configure very slow, since the whole xen >>>> image is linked for every test. >>> >> [ snip ] > > Well in any case I think we do need to do the complete link in each > test. Perhaps there is a way to make it faster. There's now specs.configure that attempts to link only the parts used by "userspace" instead of the entire kernel. It's about 3-4x times faster on my host, but still noticeably slower than regular ./configure. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
