This is the mail archive of the
mailing list for the binutils project.
Re: TARGET undefined in bucomm.c
Ok this makes sense now. Thank you for helping me figure this out.
On Wed, Jun 8, 2011 at 11:01 AM, Ian Lance Taylor <firstname.lastname@example.org> wrote:
> Luke <email@example.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.
"Those who would give up essential liberty to purchase a little
temporary safety deserve neither liberty nor safety."
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759