Hi Dave,

This could be an issue where your python resolves to python3 instead of python2.7.

The kernel is supposed to build with either, but it seems that the regression for building with python3 had itself broken and was only using python.  For an immediate fix that doesn't involve using docker, you can change the line in kernel/CMakeLists.txt: 

set(PYTHON "python" CACHE INTERNAL "")
set(PYTHON "python3" CACHE INTERNAL "")


From: Devel <devel-bounces@sel4.systems> on behalf of Mike Clark <undefinedspace@gmail.com>
Sent: Wednesday, December 5, 2018 12:32 PM
To: Dave Richards
Cc: devel@sel4.systems
Subject: Re: [seL4] Building seL4x86_64 on Debian
Any reason you aren't using the Docker image to build everything?


On Tue, Dec 4, 2018, 8:26 PM Dave Richards <dave@synergy.org wrote:

I thought I got all of the host dependencies installed, but evidently I am doing something wrong.  I am building on Debian 9 (x86_64) system.  I ran the init script from the build directory with the –DPLATFORM=x86_64 and –DSIMULATION=0 options.  I then ran ninja with no options.  Please find attached the output of running these 2 steps.  I’d appreciate a gentle nudge in the right direction.






Devel mailing list