Date: Mon, 6 Mar 2000 09:52:01 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Jeff Williams cc: djgpp AT delorie DOT com Subject: Re: install -> ginstall symlink in fil316b In-Reply-To: <200003051710.LAA10885@darwin.sfbr.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 5 Mar 2000, Jeff Williams wrote: > `install' is a symlink that comes with the fil316b.zip archive, > and it points to `ginstall.exe'. The symptom is as follows: > > % ginstall --version > install (GNU fileutils) 3.16 > > % install --version > ./GINSTALL.EXE: cannot open This is a known bug: install.exe was created with DJGPP v2.01, and the stub back then could not handle ``symlink'' targets with exactly 8 characters in their basename. The bug was corrected long ago, but until Fileutils are ported again, it will not propagate... > % ln -s ginstall.exe gi.exe > % gi --version > install (GNU fileutils) 3.16 > > So what is the difference between `install' and my `gi'? `gi' was created by stubify from DJGPP v2.03, whose built-in stub has this bug fixed. That's why it works. Simply overwrite install.exe with your gi.exe, and the problem will go away. Incidentally, I think it's not a good idea to use `install' on DOS/Windows systems anyway: you could easily pick up the Windows install.exe, what with the brutal Windows way of sticking its own directories to the front of PATH (unless you use special work-arounds for this misfeature in your AUTOEXEC.BAT). So I think using `ginstall' is better even without this bug. (Why do you think all Makefile's in ports of GNU utilities use ginstall? ;-)