Date: Sun, 27 Jun 1999 18:39:27 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Wei-Xue Shi cc: djgpp AT delorie DOT com Subject: Re: Why are there *.exe and g*.exe in fileutils3.16 In-Reply-To: <7l3t8o$f8j$1@news.telewaynet.ad.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 27 Jun 1999, Wei-Xue Shi wrote: > I installed the fileutils3.16 in my computer with Windows98. > But the install.exe doesn't work, it gives me the message > C:\DJGPP\BIN\GINSTALL.EXE: cannot open This is due to a bug in the library used to compile the ported Fileutils. Use ginstall instead. > I fund in C:\DJGPP\BIN there are install.exe and ginstall.exe, > mkdir.exe and gmkdir.exe, rmdir.exe and grmdir.exe. Why > are there such *.exe and g*.exe. The g*.exe programs are for use from the DOS prompt, since rmdir and mkdir are internal (and much more inferior) commands of COMMAND.COM, so it will invoke those internal commands instead of the programs. However, if a Makefile or another DJGPP program invokes a command like "rmdir", the library functions that run external commands will look for .exe programs first. Thus, for example, Unix Makefile that need the additional functionality not found in COMMAND.COM's commands still work. ginstall was provided because too many programs on a typical DOS/Windows machine are called install.exe. > Which should I use? You can use either one, grmdir and gmkdir are simply ``symlinks''. install has a problem, so use ginstall. > I tried to get help from doc files but nothing. I guess you didn't read the file gnu/filutil3.16/djgpp/README that comes with the distribution, since it explains this.