Mail Archives: djgpp-workers/2003/03/18/09:10:10
Hello.
Martin Stromberg wrote:
>
> > Yes. I'm using bash 2.04.
> >
> > bash-2.04$ echo $PATH
> > c:/djgpp/bin;c:/users/rich/bin;c:/windows;c:/windows;c:/windows/command;c:/djgpp/bin;c:/windows;c:/windows/command;c:/utils/toolbox;c:/djgpp/gnu/emacs/bin;c:/progra~1/doxygen/bin
>
> Just to verify I'm not blind or something: you do not have . in the
> PATH, right?
Yes, there's no "." in my PATH.
> If you make some little program in tmp/ say silly.exe and go there and
> type "silly" and "silly.exe" it says command not found, right?
Yes, it's not found.
> If not, then it looks like your bash is broken... (Unlikely.)
>
> If yes, there's something else different in my environment. Perhaps
> SHELL=e:/djgpp/bin/-bash.exe (unsure about the "-")?
My shell is set to COMMAND.COM. I don't set SHELL in the environment. It has
its default setting.
> Since it works for you I suspect you manage to spawn COMMAND.COM from
> the makefile, because the makefile tries to run the program like
> "test" (I don't remember the exact name) which is broken because PATH
> shouldn't include "." or at least the makefile should not count on
> it.
>
> Perhaps another correction would be adding "SHELL=/bin/sh" too? (IIRC,
> this would force make to run bash, right?)
No, it does not run bash. SHELL=/bin/sh forces make to emulate certain Unixy
features. See the sectione entitled ""SHELL=/bin/sh" -- or is it?" in
gnu/djgpp/make-*/readme.dos.
But yes, this is a reasonable correction:
SHELL=/bin/sh make all
works for me.
But is this change OK for the other compilation environments mentioned in the
Makefile - TURBOC, etc. Do we care about them?
> If you do, does it break for you?
SHELL=/djgpp/bin/bash.exe make all
does not work for me.
PATH="$PATH;." SHELL=/djgpp/bin/bash.exe make all
does work for me.
Bye, Rich =]
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
- Raw text -