There should be many more flags passed to `gcc`, including some -I
flags and some -D flags.
Is something in your environment overriding the CFLAGS definition in
the makefile? Normally, a definition in the makefile would take
precedence over an environment variable, but maybe something else is
taking precedence over the definition?
At Sat, 08 Feb 2014 21:46:37 +, Paulo J. Matos wrote:
Hello,
If I grab racket HEAD and try to compile it with:
git clone ... racket.git
cd racket/racket/src
mkdir build
cd build
../configure --prefix=...
make -j16
I get:
make[6]: Entering directory
`/home/pmatos/work/racket/racket/src/build/racket/gc'
gcc -O0 -g3 -c ../../../racket/gc/alloc.c
gcc -O0 -g3 -c ../../../racket/gc/reclaim.c
gcc -O0 -g3 -c ../../../racket/gc/allchblk.c
../../../racket/gc/alloc.c:19:30: fatal error: private/gc_priv.h: No
such file or directory
# include private/gc_priv.h
gc/ has an include/private directory so I would have expected the
command line to gcc to be something like:
gcc -O0 -g3 -c ../../../racket/gc/alloc.c -Iinclude/
Also, when I try simply:
make
I get:
make[6]: Entering directory
`/home/pmatos/work/racket/racket/src/build/racket/gc'
rm -f mach_dep.o
./if_mach SPARC SOLARIS gcc -c -o mach_dep2.o
../../../racket/gc/sparc_mach_dep.S
make[6]: ./if_mach: Command not found
make[6]: *** [mach_dep.o] Error 127
The if_mach script exists in racket/gc but not in the build/racket/gc so
I guess somewhere there needs to be a copy of the script onto the build
directory. I am curious how you guys usually do the build if not like
this...
--
PMatos
_
Racket Developers list:
http://lists.racket-lang.org/dev
_
Racket Developers list:
http://lists.racket-lang.org/dev
