Date: Tue, 6 Oct 1998 20:21:50 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: problem with install.exe in fil316b.zip
In-Reply-To: <Pine.GSO.4.05.9810051706490.24189-100000@rtbsci146s>
Message-ID: <Pine.SUN.3.91.981006201609.18745D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Mon, 5 Oct 1998, Olivier Perron wrote:

> In the fil316b.zip package, install.exe seems to be a symlink to 
> ginstall.exe.
> 
> If I execute: install my_prog.exe destdir
> I have the following error: C:\USR\BIN\GINSTALL.EXE : cannot open

It is a known bug in the stub of v2.01: if the target of a ``symlink'' has
exactly 8 characters in its name, the symlink doesn't work.  This bug is
on the two reason that most of the ports of GNU packages are configured 
with INSTALL='ginstall -c' option.  (The other reason is that there are 
too many programs named install.exe on a typical DOS/Windows system, so I 
would suggest to always invoke ginstall from the command line.)

This bug will be corrected in v2.02, but in the meantime just run
`ginstall' directly, that's all. 

An alternative would be to rename ginstall.exe to something else, and 
stubedit install.exe to run that image, but that might break your ability 
to configure and build other GNU packages (see above).

Yet another way is to rename ginstall.exe to install.exe, but I explained 
above why this might be dangerous.