From: Jeff G. <jef...@po...> - 2003-12-21 23:23:02
|
Hi All, I have a directory full of (non-Msys) command line development tools - some of which overlap the tools provided Msys (grep, make, etc). For the project I am working on, I am required to use these (other) tools, but I'd like to do it from within the BASH shell provided by Msys. The problem is, every time I try to run *any* of these tools from within the Msys BASH shell, I get a "Permission denied" error (I am cd'ing into the directory containing the tool and doing a "./<tool.exe>"). If, on the other hand, I open a DOS shell, cd to the same directory, and run the tool - all works as expected. Any idea why the tools won't run from within the Msys BASH shell? I've copied other executables into the directory in question (like wordpad.exe), and they've run correctly - which seems to eliminate any weird permission problems on the directory tree. MSYS 1.0.1.0 / WinXP Professional Thanks for any input. Jeff Godfrey |
From: Earnie B. <ea...@us...> - 2003-12-22 14:05:42
|
What dll's exist in your tools directory? Do the commands work when not in the tools directory? Earnie. Jeff Godfrey wrote: > Hi All, > > I have a directory full of (non-Msys) command line development tools - some > of which overlap the tools provided Msys (grep, make, etc). For the project > I am working on, I am required to use these (other) tools, but I'd like to > do it from within the BASH shell provided by Msys. The problem is, every > time I try to run *any* of these tools from within the Msys BASH shell, I > get a "Permission denied" error (I am cd'ing into the directory containing > the tool and doing a "./<tool.exe>"). If, on the other hand, I open a DOS > shell, cd to the same directory, and run the tool - all works as expected. > Any idea why the tools won't run from within the Msys BASH shell? > > I've copied other executables into the directory in question (like > wordpad.exe), and they've run correctly - which seems to eliminate any weird > permission problems on the directory tree. > > MSYS 1.0.1.0 / WinXP Professional > > Thanks for any input. > > Jeff Godfrey > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > -- http://www.mingw.org <http://sourceforge.net/projects/mingw> |
From: Jeff G. <jef...@po...> - 2003-12-22 14:25:36
|
From: "Earnie Boyd" <ea...@us...> > What dll's exist in your tools directory? None... Here is the entire directory contents... 386LIB.EXE* 386LINK.EXE* 486.INC CFIG386.EXE* CLRFILE.CV4 CURRENT.STS DBGLIB.REX ENGLISH.CER ENGLISH.EER F77L3.3IG F77L3.4IG F77L3.CER F77L3.EER F77L3.EXE* F77L3.FIX FFTOSTD.EXE* FIG3.EXE* FIG3.HLP FILES.EXE* GORUN386.EXE* GREP.EXE* LAHEY.INC LB.CFG LB.COM* LB.KEY LB.LNG LB.PST LB.SGD LB.SGX LBOVL.EXE* M.TMP MAKE.EXE* MAKE.INI MAKEFILE MAKEFILE.LIB MAKEFILE.PRG MAKEL.EXE* MKMF.EXE* MSOFT.INC PHARLAP.386* RUN3.BAT* RUN386.EXE* SOLD3.EXE* SOLD3.MSG SOLD3VM.EXE* STDTOFF.EXE* SUN.INC TELLME.EXE* TOOLS.002 TOOLS.INI TOUCH.EXE* VI.INI VISTRNGS VMM.EXP f77l3.fig make.PIF make_lahey.PIF > Do the commands work when not in the tools directory? No, they don't. Jeff |
From: Earnie B. <ea...@us...> - 2003-12-22 15:00:07
|
These appear to be 16bit dos programs. Does ``cmd //c 386link'' execute the command? Earnie. Jeff Godfrey wrote: > From: "Earnie Boyd" <ea...@us...> > > >>What dll's exist in your tools directory? > > > None... > > Here is the entire directory contents... > > 386LIB.EXE* > 386LINK.EXE* > 486.INC > CFIG386.EXE* > CLRFILE.CV4 > CURRENT.STS > DBGLIB.REX > ENGLISH.CER > ENGLISH.EER > F77L3.3IG > F77L3.4IG > F77L3.CER > F77L3.EER > F77L3.EXE* > F77L3.FIX > FFTOSTD.EXE* > FIG3.EXE* > FIG3.HLP > FILES.EXE* > GORUN386.EXE* > GREP.EXE* > LAHEY.INC > LB.CFG > LB.COM* > LB.KEY > LB.LNG > LB.PST > LB.SGD > LB.SGX > LBOVL.EXE* > M.TMP > MAKE.EXE* > MAKE.INI > MAKEFILE > MAKEFILE.LIB > MAKEFILE.PRG > MAKEL.EXE* > MKMF.EXE* > MSOFT.INC > PHARLAP.386* > RUN3.BAT* > RUN386.EXE* > SOLD3.EXE* > SOLD3.MSG > SOLD3VM.EXE* > STDTOFF.EXE* > SUN.INC > TELLME.EXE* > TOOLS.002 > TOOLS.INI > TOUCH.EXE* > VI.INI > VISTRNGS > VMM.EXP > f77l3.fig > make.PIF > make_lahey.PIF > > >>Do the commands work when not in the tools directory? > > > No, they don't. > > Jeff > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > -- http://www.mingw.org <http://sourceforge.net/projects/mingw> |
From: Jeff G. <jef...@po...> - 2003-12-22 16:20:46
|
----- Original Message ----- From: "Earnie Boyd" <ea...@us...> To: <min...@li...> Sent: Monday, December 22, 2003 9:04 AM Subject: Re: [Mingw-msys] Permission Denied Error > These appear to be 16bit dos programs. > > Does ``cmd //c 386link'' execute the command? Earnie - yes, it does. So, is this the "correct" way to run these programs from the Msys BASH shell? If so, how would the following DOS line translate? c:\F77L3\bin\make.exe comp=msoft32 I tried this: cmd //c /c/F77L3/bin/make.exe comp=msoft32 but it doesn't seem to quite work as expected. It's almost like the "comp=..." argument is not getting through correctly... Basically, I'm trying to put together a BASH script to replicate the above DOS line (among other things). Any other advice appreciated. Thanks, Jeff |
From: Earnie B. <ea...@us...> - 2003-12-22 18:35:32
|
What version of MSYS? Jeff Godfrey wrote: > ----- Original Message ----- > From: "Earnie Boyd" <ea...@us...> > To: <min...@li...> > Sent: Monday, December 22, 2003 9:04 AM > Subject: Re: [Mingw-msys] Permission Denied Error > > > >>These appear to be 16bit dos programs. >> >>Does ``cmd //c 386link'' execute the command? > > > Earnie - yes, it does. So, is this the "correct" way to run these programs > from the Msys BASH shell? > > If so, how would the following DOS line translate? > > c:\F77L3\bin\make.exe comp=msoft32 > > I tried this: > > cmd //c /c/F77L3/bin/make.exe comp=msoft32 > > but it doesn't seem to quite work as expected. It's almost like the > "comp=..." argument is not getting through correctly... > Using my regression binary I see <stdio> $ ./mingw32-echo.exe comp=msoft32 comp=msoft32 </stdio> So it should work. > Basically, I'm trying to put together a BASH script to replicate the above > DOS line (among other things). > > Any other advice appreciated. > So, what I'll suggest if you get it working is to create a script or scripts to execute the binaries. <script name="/usr/local/bin/f77l3-make"> #!/bin/sh cmd //c c://F77L3/bin/make.exe "$@" </script> Then you would do ``f77l3-make comp=msoft32''. Earnie -- http://www.mingw.org <http://sourceforge.net/projects/mingw> |
From: Jeff G. <jef...@po...> - 2003-12-22 18:42:25
|
Subject: Re: [Mingw-msys] Permission Denied Error Date: Mon, 22 Dec 2003 12:34:39 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Disposition-Notification-To: "Jeff Godfrey" <jef...@po...> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 ----- Original Message ----- From: "Earnie Boyd" <ea...@us...> To: <min...@li...> Sent: Monday, December 22, 2003 12:40 PM Subject: Re: [Mingw-msys] Permission Denied Error > What version of MSYS? 1.0.10 |
From: Earnie B. <ea...@us...> - 2003-12-22 21:29:00
|
Jeff Godfrey wrote: > > 1.0.10 > Describe the problems? I don't see that it should be a problem. You may need to create an executable with your compiler/linker that dumps the arguments as they were received to determine the differences. Earnie. -- http://www.mingw.org <http://sourceforge.net/projects/mingw> |