[email protected] said: > "obsolete" is a dangerous term when it comes to autoconf. > decade-old configure scripts are not rare in the real world.
Personally I think the current -configure wrapper should go away and users should just cross compile using whatever method works best for their software. If that means settng CC= then do that, or use --host=. CMake and others again have their own way of doing it. > On irc I managed to extract from mato that this means e.g. > arm-rumprun-netbsd-gcc. Then mato shot to dinner; I'm not sure if > that's lacking "xen" and "baremetal" by design or accident. I'm a > big fan of not exposing information where it's not necessary, but I > didn't think his proposal through, so not sure if they absolutely > should be there or not. Back from dinner :-) See my other email about why including these is problematic. We had this discussion back in January and I don't have an opinion either way. We could possibly stuff the 'platform' into the 'vendor' part of the "old form" autoconf string, but that doesn't feel right. > Anyway, the vibe I'm guessing is that the description matches the > tool wrappers already created by buildrump.sh. If at all possible, > I think we should enhance buildrump.sh wrapper creation instead of > having two sets of subtly different cross compilers. That would > also unify the "kernel" and "userland" build, which is a direction > I'd like to see us going into, i.e. fixing the dichotomies which > were created when "userland" was invented ... Sounds good. Could an outcome of that be that xen and baremetal built for the same target would be able to share a single rumpobj tree? (Not sure if this is a good idea or not, just curious if it is possible) >
