search for: rumpkernel

...ummary of why it matters that the answer is yes) e.g. I have aarch64-linux-gnu-{gcc,as,ld,ar,etc} which I can use to build aarch64 binaries on my x86_64 host, including picking up aarch64 libraries and headers from the correct arch specific patch. Do these rumprun-provided wrappers provide x86_64-rumpkernel -{gcc,as,ld,ar,etc} ? Appearing as a regular cross-compilation target is, I think, going to be important to being able to create rumpkernel based versions of distro packages. I think that package maintainers ideally won't want to have to include a bunch of rumpkernel specific code in their pa...

...; unikernels such as routers and firewalls. But, for brevity and simplicity, I'll assume the POSIX'y mode for the rest of this email, since that's what the QEMU stubdom will no doubt use. If the above didn't explain the grand scheme of things clearly, have a look at http://wiki.rumpkernel.org/Repo and especially the picture. If things are still not clear after that, please point out matters of confusion and I will try to improve the explanations. Also for simplicity, I'll be talking about rump kernels constructed from the NetBSD kernel, and the userspace environment of Rump...

...t the answer is yes) > > e.g. I have aarch64-linux-gnu-{gcc,as,ld,ar,etc} which I can use to build > aarch64 binaries on my x86_64 host, including picking up aarch64 libraries > and headers from the correct arch specific patch. > > Do these rumprun-provided wrappers provide x86_64-rumpkernel > -{gcc,as,ld,ar,etc} ? No, like I said and which you discovered later, x86_64-rumprun-netbsd-{gcc,as,ld,ar,etc}. aarch64 would be aarch64-rumprun-netbsd-{...}. > Appearing as a regular cross-compilation target is, I think, going to be > important to being able to create rumpkernel ba...

...e aarch64-linux-gnu-{gcc,as,ld,ar,etc} which I can use to > > build > > aarch64 binaries on my x86_64 host, including picking up aarch64 > > libraries > > and headers from the correct arch specific patch. > > > > Do these rumprun-provided wrappers provide x86_64-rumpkernel > > -{gcc,as,ld,ar,etc} ? > > No, like I said and which you discovered later, > x86_64-rumprun-netbsd-{gcc,as,ld,ar,etc}. aarch64 would be > aarch64-rumprun-netbsd-{...}. Sorry, I used an explicit example when really I just meant "some triplet" without saying "...

...build a bootable image, perhaps capable of running either on Xen or > KVM. > > That's obviously not going to happen overnight -- but it would be > interesting for Someone to give a try, just to see how difficult it is. > If it's not that difficult to build libraries against rumpkernels and > package them up so they can be linked to from applications, then the > road to Debian / Fedora-built unikernel applications (including qemu) > may not actually be that long. ----------------------------------------------------------------------- Wei and I both replied. Wei said:...

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

Hello LLVM Developers, Within Google, we have a growing range of needs that existing libc implementations don't quite address. This is pushing us to start working on a new libc implementation. Informal conversations with others within the LLVM community has told us that a libc in LLVM is actually a broader need, and we are increasingly consolidating our toolchains around LLVM. Hence, we