Not sure why the most recent commit to the experimental branch of the kernel didn't
get pushed out, but that was causing the majority of your problems. I also updated the
c162_twovm_defconfig to fix some more build errors.
Should build without problems now.
On Tue 07-Jun-2016 2:15 AM, Samuel Weiser wrote:
didn't manage to build camkes-vm. Is there any working setup available or did I make
I tried to build c162_twovm_defconfig with the "default.xml" manifest
1a.) I get compile errors regarding some definitions of seL4_X86.... It seems that
seL4_libs (March 2016) are inconsistent with the kernel version (Dec 2015). Updating to a
newer kernel, i.e. 3.1.0 solves this issue but creates new ones:
The bootinfo struct is too big to fit one page.
I get the error: compile_assert(bi_size, sizeof(seL4_BootInfo) <=
So I reduced the max. no of bootinfo untyped caps from 800 to 167
Error: No rule to make target 'libsel4simple-default', needed by
Since the kernel is not stable, it falls back to default but does not manage to correctly
reference the default lib. First, I added the missing symlink in libs. Then, I added the
default lib to the main Kconfig and the apps/c162_twovm/Kbuild.
The next error is:
x86/pc99/include/vmm/guest_state.h:60:44: error: unknown type name ‘seL4_VCPUContext’
I also tried building with the "working.xml" manifest, which already failed to
fetch the correct revisions
In the working.xml, I fixed the seL4_libs upstream to 'master'
Also, the kernel revision is broken, seL4.git points to an experimental commit, which
couldn't be fetched. I changed it to kernel 3.1.0.
The same error as in 1d) appears. This is where I gave up.
Thanks in advance,
Devel mailing list
The information in this e-mail may be confidential and subject to legal professional
privilege and/or copyright. National ICT Australia Limited accepts no liability for any
damage caused by this email or its attachments.