l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <m...@netris.org> skribis:
>
>> I agree that this is fragile and should be reworked somehow, but for
>> 2.0.10, I wonder if we could just revert the part of 8cb0d6d having to
>> do with gen-scmconfig.c.
>>
>> What do you think?
>
> You’re right. So for 2.0.10, just revert, and then remove #include
> <config.h> altogether in c-tokenize.lex with a comment saying why.
I don't think we can remove it altogether. On some non-GNU systems,
some Gnulib's headers complain if we haven't yet included <config.h>.
This was the motivation for e1bb79fde62e678c0f8ceb32c7edd2dab0201a5c,
where you moved the "#include <config.h>" to the top of the c-tokenize.
Dale Evans pointed out that GCC runs the autoconf tests twice when
cross-compiling: once for the build machine and once for the host
machine. I suspect that this is the proper solution for us, so we'd
end up with two config.h files.
> (BTW, we can test cross-compilation to GNU/Linux with
> guix build guile --with-source=guile-2.0.9.xyz.tar.xz
> --target=mips64el-linux-gnu.)
Nice! I can use this to test any proposed solution(s) we come up with.
Thanks,
Mark
