search for: foocc

...provide. That way we > don't have to figure out where to get a toolchain which produces binary > for every target that everyone might want. Also, it makes bootstrapping > Rumprun convenient, since you just say "hey give me the components and > application wrappers for CC=foocc" and off you go. > The produced wrappers look exactly like a normal cross-toolchain. The > tuple is the same as what NetBSD uses, except with rumprun added in the > middle, so e.g. x86_64-rumprun-netbsd or arm-rumprun-netbsdelf-eabihf. Great, I think this solves a large problem...

...ny toolchain (*) you provide. That way we don't have to figure out where to get a toolchain which produces binary for every target that everyone might want. Also, it makes bootstrapping Rumprun convenient, since you just say "hey give me the components and application wrappers for CC=foocc" and off you go. *) as long as it's gcc-derived, for now (IIRC gcc 4.8 - 5.1 are known to work well, older than that at least C++ won't work). clang doesn't support specs files at least AFAIK, so someone would have to figure out how to move the contents of the specs into the w...

Xen upstream BoF ================ We had a discussion around Xen and packaging at Debian's annual developer conference (Debconf) a few weeks back: https://summit.debconf.org/debconf15/meeting/279/xen-upstream-bof/ These are my notes, I think there is probably stuff of interest to most distro people, not just Debian folks. The session was scheduled in a small, out of the way, room. Around 2