This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: TARGET undefined in bucomm.c
Luke <hazelnusse@gmail.com> writes:
> but not when building bucomm.c. So config.h *isn't* being included,
> for some reason. I don't know which config.h is being included by
> alloca-conf.h, but it isn't the generated binutils/config.h. The only
> major difference I can see is the -I flags. Could this have something
> to do with it?
Run something like
make CFLAGS="-g -O2 --save-temps" bucomm.o
That will create, besides bucomm.o, a file bucomm.i. In the first 20
lines of bucomm.i you should see an entry for config.h. Where is
config.h being found?
When I try it, I see the appended, which shows config.h being included
from the binutils build directory, as expected.
Ian
# 1 "../../src/binutils/bucomm.c"
# 1 "/home/iant/binutils/objdir/binutils//"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "../../src/binutils/bucomm.c"
# 26 "../../src/binutils/bucomm.c"
# 1 "../../src/binutils/sysdep.h" 1
# 25 "../../src/binutils/sysdep.h"
# 1 "../../src/binutils/../include/alloca-conf.h" 1
# 1 "./config.h" 1
# 2 "../../src/binutils/../include/alloca-conf.h" 2
# 1 "/usr/include/alloca.h" 1 3 4
# 22 "/usr/include/alloca.h" 3 4
# 1 "/usr/include/features.h" 1 3 4