TARGET undefined in bucomm.c

[Ian Lance Taylor]

Luke <hazelnusse@gmail.com> writes:

> So, am I correct in understanding that C_INCLUDE_PATH should not have
> a trailing colon, and if it does, it may wreak havoc on things in
> non-obvious ways?  Might this be a bug in how gcc (or some other part
> of the build process) parses the environment variables?

In any PATH variable, a trailing (or leading) colon means the current
directory (i.e., ".").  In this case it was breaking things because it
meant that the explicit -I. command line option was being discarded as a
duplicate, and so "." was being searched at the wrong point in the
search path.

Ian