Re: Upgrading toolchain gcc to 7.2

Thanks for the answer.

I have already tried to follow the commands in README.mknative, but it seems I'm doing something wrong.

On the host (!= target) I have trouble executing step 3: In src/tools/gcc, do "nbmake-MACHINE HAVE_GCC=48 bootstrap-libgcc".

The command I run: ../../../obj.netbsd/tooldir.Linux-4.13.3-1-ARCH-i686/bin/nbmake-evbearm-el MKGCCCMDS=yes HAVE_GCC=48 bootstrap-libgcc

is failing with the reason:

checking how to run the C preprocessor... /lib/cpp
configure: error: in `/home/rchmiela/experiments/obj.netbsd/tools/gcc/build/arm--netbsdelf-eabi/libgcc':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
nbgmake: *** [configure-target-libgcc] Error 1

Should I be running this command on target? Or maybe it's the fault of my host gcc (7.2.0)?

Cheers,

Radek

2018-01-09 9:20 GMT+01:00 Martin Husemann <martin%duskware.de@localhost>:

On Tue, Jan 09, 2018 at 08:22:25AM +0100, rchmielarz . wrote:
> 3) A more general question about the build system. I understand that
> /tools/gcc has the makefiles for building the cross-compilation toolchain.
> But what is the purpose of /external/gpl3/gcc/lib and usr.bin. Why do they
> have to be separate from the ../dist? And how have You came up what files
> to include in those tools?

I can't really tell the purpose of other patches (unless they are explained
in the commit log), but this part I can explain:

We do not want to run autoconfig like things as part of the regulary build.
We use them for building the tools part, but after that, everything should
be strictly reproducable and not influenced by host system details.

So we pre-run those, and commit the results.

I guess the best start to understand the procedure is:

src/tools/gcc/README.mknative

Martin