gcc.c #v+ [...] Specs are strings containing lines, each of which (if not blank) is made up of a program name, and arguments separated by spaces. The program name must be exact and start from root, since no path is searched and it is unreliable to depend on the current working directory. [...] #v-
On further inspection of `gcc.c' it turns out that this is not true, and instead a rather extensive method of locating the executable is used, involving hard-coded paths and also `$PATH'. #v+ $ cat specs @foo_language: printenv PATH which fortune fortune $ gcc -E -x foo_language -specs=specs /dev/null /home/cip/3/cpts2523/command:/home/cip/3/cpts2523/shared/command:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games /usr/games/fortune But, for my own part, it was Greek to me. -- William Shakespeare, "Julius Caesar" #v- -- Summary: Incorrectness in `gcc.c' Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tschwinge at gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30090