Closed axel-h closed 3 years ago
Yea, I agree that the real bug is in seL4/seL4
So let's include autoconf.h
in sel4/config.h
unconditionally then?
OK, so once https://github.com/seL4/seL4/pull/300 is merged, we can drop this PR
dropping this PR , as the too cause is fixed now.
I'm getting this error
and a similar one for
CONFIG_MAX_NUM_BOOTINFO_UNTYPED_CAPS
andCONFIG_NUM_DOMAINS
. The explanation is, that in kernel commit https://github.com/seL4/seL4/commit/1ce721b418f13e7430d379461c59b80322fc6daf the filesel4/config.h
was extended to make the kernel configuration available to user space. However, it will includeautoconf.h
only ifHAVE_AUTOCONF
is defined and provide a fixed default configuration otherwise. We don't defineHAVE_AUTOCONF
anywhere, but includeautoconf.h
unconditionally instead everywhere, which leads to conflicting defines if this include is forgotten. Thus we add the missing includeautoconf.h
here before includingsel4/config.h
then.We could also define
HAVE_AUTOCONF
, but I wonder if this should be considered deprecated and get removed everywhere eventually. We no longer use autoconf and CMake just mimics it keep compatibility. I wonder if there is any need for all the compatibility layers left nowaday and the change insel4/config.h
are another step away form this actually. IfHAVE_AUTOCONF
gets fully removed, all project could just includesel4/config.h
instead of the atticautoconf.h
.Note that we could also avoid this PR if we change
sel4/config.h
and replacewith simply
but I wonder which additional side effects this has in other modules. So merging this PR here might be the quicker way to avoid the current problem before trying to solve this in a more general way.