I cannot give any useful insight, and am secretly hoping that someone
lurking on this list will have good comments, so since I "need" to say
something anyway, I'll resort to while-we're-renaming
bikeshedding/threadjacking.
On 05/05/15 10:07, Martin Lucina wrote:
Hi all,
this is hopefully the final thread regarding app-tools toolchain naming.
Do we want to keep the name "app-tools"? AFAIR, it was coined (by Ian?)
before we'd really settled in on other terminology. Is simply
rumprun-tools better?
Therefore, I'd like to propose that we the following scheme for
naming both the filesystem "arch prefix" and "arch tuple" passed to
configure:
<cpu>-rumprun{posix,xen,baremetal}-<kernel+userland>
I'm a bit unhappy with "baremetal". It's long and not very descriptive.
At least we'll get rid of the extra "bmk" term, which is good, but a
better term for "baremetal" would be nice to invent.
Where <kernel+userland> is currently "netbsd", i.e. the existing "native"
value is re-used for this field.
Should that be "netbsdelf" for i386 (and other NetBSD targets which
originally used a.out)?
I'd like to get the renaming done ASAP, so if anyone has objections to
the proposed scheme please speak up now! Final call :-)
How many real programs have you tested the scheme with?
Thanks for taking the time to do a thorough investigation!
- antti
