v850 simulator build issue

[Joel Sherrill]

Hi

We have a build failure for the v850 simulator on a FreeBSD
host to run on mingw because igen/configure.ac does this

$ grep gcc * | grep -v ure:
configure.ac: CC_FOR_BUILD=${CC_FOR_BUILD-gcc}

There is no gcc on FreeBSD 10

gcc -O2 -pipe -fbracket-depth=1024 -I/mnt/data0/chrisj/rtems/rsb/rtems-source-builder.master/rtems/build/tmp/sb-chrisj/4.11/rtems-v850.bset/opt/rtems/4.11/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wno-pointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Wformat-nonliteral -I. -I../../../gdb-7.7/sim/igen -I../../../gdb-7.7/sim/igen/../../include -c ../../../gdb-7.7/sim/igen/igen.c
gmake[4]: gcc: Command not found


Any suggestion on the correct modification to pick up
either cc or gcc?

[Ralf Corsepius]

Post by Joel Sherrill
Hi
We have a build failure for the v850 simulator on a FreeBSD
host to run on mingw because igen/configure.ac does this
configure.ac: CC_FOR_BUILD=${CC_FOR_BUILD-gcc}
There is no gcc on FreeBSD 10
gcc -O2 -pipe -fbracket-depth=1024 -I/mnt/data0/chrisj/rtems/rsb/rtems-source-builder.master/rtems/build/tmp/sb-chrisj/4.11/rtems-v850.bset/opt/rtems/4.11/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wno-pointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Wformat-nonliteral -I. -I../../../gdb-7.7/sim/igen -I../../../gdb-7.7/sim/igen/../../include -c ../../../gdb-7.7/sim/igen/igen.c
gmake[4]: gcc: Command not found
Any suggestion on the correct modification to pick up
either cc or gcc?

.../configure CC_FOR_BUILD=clang
or
.../configure CC_FOR_BUILD=cc
or similar should do.

Ralf

[Mike Frysinger]

Post by Joel Sherrill
We have a build failure for the v850 simulator on a FreeBSD
host to run on mingw because igen/configure.ac does this
configure.ac: CC_FOR_BUILD=${CC_FOR_BUILD-gcc}

this isn't specific to igen. if you look through the tree, you'll see this
pattern duplicated many times. it'd be nice if there was a single m4 in
config/ so we'd just call that, and then i think you could make a reasonable
argument for expanding the default CC_FOR_BUILD search path to be more like
the existing AC_PROG_CC.

would be even nicer if autoconf itself had a AC_PROG_BUILD_CC (or however you
want to name it), but let's start in the pond we control :).
-mike