This is the mail archive of the
mailing list for the GCC project.
[Bug c/37995] using <stdio.h> fails if gcc invoked in a directory which has a subdirectory called "gcc"
- From: "mvanier at cs dot caltech dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Nov 2008 11:07:34 -0000
- Subject: [Bug c/37995] using <stdio.h> fails if gcc invoked in a directory which has a subdirectory called "gcc"
- References: <email@example.com/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from mvanier at cs dot caltech dot edu 2008-11-04 11:07 -------
OK, I built a vanilla gcc system from scratch and it's still exhibiting the
same problem. However, here's something new: the problem only manifests itself
if "." (the current directory) is in the path. If it isn't, no problem.
$GCC_EXEC_PATH is not defined.
Also, (when "." is in the path) if I explicitly give the path to gcc:
% /pkg/gcc/bin/gcc hello.c
it works. But if I don't:
% which gcc
% gcc hello.c
you get the same error message I reported before. This is really weird.