Nevermind I fixed this error and everything seems to be working perfectly. Thanks for the support. Looks like have sh.exe in my PATH was the issue.
Thanks, Brandon ________________________________ From: Loch Brandon <lochbran...@johndeere.com> Sent: Friday, May 8, 2020 10:13 AM To: Eli Zaretskii <e...@gnu.org> Cc: psm...@gnu.org <psm...@gnu.org>; bug-make@gnu.org <bug-make@gnu.org> Subject: Re: Windows shell discovery (was: Re: Incorrect path and shell script error) Yes I did have sh.exe in my path. I removed it and this is what the following output was. C:\Users\bl68969.JDNET\Projects\HHP2\Code\M2_501\ProgramSpecific\MakeFileBuild>make ------------------------------------------------------------------------------ Verifying and building application directory structure... ------------------------------------------------------------------------------ was unexpected at this time. make: *** [dirs] Error 255 ________________________________ From: Eli Zaretskii <e...@gnu.org> Sent: Friday, May 8, 2020 9:46 AM To: Loch Brandon <lochbran...@johndeere.com> Cc: psm...@gnu.org <psm...@gnu.org>; bug-make@gnu.org <bug-make@gnu.org> Subject: Re: Windows shell discovery (was: Re: Incorrect path and shell script error) > From: Loch Brandon <lochbran...@johndeere.com> > CC: "psm...@gnu.org" <psm...@gnu.org>, "bug-make@gnu.org" <bug-make@gnu.org> > Date: Fri, 8 May 2020 14:42:31 +0000 > > Sorry I wasn't clear. I added the following command > SHELL := C:\Windows\System32\cmd.exe (which is what i meant by adding the > path to cmd.exe) > > I don't believe that it would be an issue with the escape characters because > there are other developers that > use this same makefile and have no issues with getting it to work. My windows > profile was recreated which I > believe lead to this issue. I'm not quite sure I know the impact that this > had to my computer and other > programs, since I have nothing to compare it to. > > The error I sent in the last email is what I get when adding the SHELL > variable into the makefile. Do you have sh.exe on PATH? If so, what happens if you remove its directory from PATH, or temporarily rename sh.exe to something like s.e? does the problem go away then?
