>> Is the suggestion to use this toolchain for rumprun now? > > You can try. If it works, use it ;-)
Back to the original issue, so I’ll try and work on that with the original
toolset...
> Well there was at least one part of crazy in my brain (as usual). I forgot
> that for a NetBSD tools build, you're using the host toolchain to build the
> actual tools and compat code. For Rumprun in your case, you're using the
> host toolchain to build a toolchain which is used to build the compat libs
> for the Rumprun case. It all gets very confusing quite quickly (at least for
> me) …
:)
There does seem to be a large amount of confusion in the OSX build about
whether it should be using the system include files or not. For instance, the
test for the xen headers fails not because the xen headers are missing (I add
the include path for that), but because the initial toolchain can’t find
stdint.h. For example:
[rickp@scampi ~]$ cat t2.c
#include <stdint.h>
#include <xen.h>
[rickp@scampi ~]$ x86_64-netbsd-gcc -Isrc/rumpkernels/xen/xen/include/public -o
/dev/null t2.c
t2.c:1:20: fatal error: stdint.h: No such file or directory
#include <stdint.h>
^
The x86_64-netbsd-gcc is built as documented at
https://github.com/rumpkernel/wiki/wiki/Howto:-Set-up-a-Rumprun-toolchain-in-Mac-OS-X.
It seems that the random inclusion (or not) of standard headers is what gives
me my previous failure (worked around by hacking
obj-amd64-*/buildrump.sh/tools/mandoc/config.h ). I can work around this in a
few places but then I hit further include problems when compiling the actual
rumpkernel.
By this time, its using the x86_64--netbsd-gcc (note the double -, subtly
different!) which is the rumprun toolchain. That runs into missing .h files
(eg. <errno.h> etc) and though I can point this at various places, it seems
like something more fundamental is wrong.
What’s the actual intention with regards to include files? Use the netbsd ones?
Cheers,
Rick
signature.asc
Description: Message signed with OpenPGP using GPGMail
