Mail Archives: djgpp-workers/1999/06/28/04:50:23
Hi, everyone.
I've not followed all of this very closely, but let me just throw in some
wild guesses that came to my mind.
On Mon, 28 Jun 1999, Andris Pavenis wrote:
> On Sun, 27 Jun 1999, Eli Zaretskii wrote:
[...]
> > One case when Make cannot invoke Bash is when something happens to PATH.
> > This causes the "SHELL = /bin/sh" line in a Makefile to be effectively
> > ignored.
>
> Yes it's really seems that problem is with PATH:
> When I used old bash-1.14.7 binary all worked Ok. After changing
> to bash-2.03 binary I found that even configure due to unknown
> reason does not find gcc.exe in D:/DJGPP/BIN (it's there, if I'm
> running it directly) but finds it in C:/DJGPP/BIN which doesn't
> work of course due to changed DJGPP env. variable.
Any possibility that inside bash, your change of PATH didn't really
happen? Have you checked what 'type gcc' says, in Bash, with both
DJGPP\BIN directories in the path? If you use bash as your 'login shell',
you might have to 'hash -r' after changing the PATH. Or this just might be
another problem with the drive letter handling in bash, I think.
> After that I removed C:/DJGPP/BIN from PATH and left only
> D:/DJGPP/BIN there. After that I got problems in form I described
> earlier (attempt to use command.com instead of bash).
A very wild guess: have you checked there actually _is_ a bash.exe and
sh.exe in d:\djgpp\bin, not only in c:\djgpp\bin, and also the usual
\bin\sh stuff on both c: and d: drivers?
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -