Message-Id: <200003051710.LAA10885@darwin.sfbr.org>
Date: Sun, 5 Mar 2000 11:10:28 -0600 (CST)
From: Jeff Williams <jeffw AT darwin DOT sfbr DOT org>
Subject: install -> ginstall symlink in fil316b
To: djgpp AT delorie DOT com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: tSMLvQu38+jFK0+c+bN6XA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.4 SunOS 5.7 sun4u sparc 
Reply-To: djgpp AT delorie DOT com

I encountered the following problem using `install' in makefiles.

`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

Strange; `install' can't find the program it is supposed to point to.
I created a new symlink `gi', and it works ok:

% ln -s ginstall.exe gi.exe
% gi --version
install (GNU fileutils) 3.16

So what is the difference between `install' and my `gi'?

% stubedit -v install.exe
-value-          -field description-
0x40000 (256k)   Minimum amount of stack space (bytes/K/M)
0x4000 (16k)     Size of real-memory transfer buffer (bytes/K/M)
GINSTALL         Base name of file to actually run (max 8 chars, ""=self)
""               Value to pass as file component of argv[0] (max 16 chars, 
""=default)
CWSDPMI.EXE      Program to load to provide DPMI services (if needed)

% stubedit -v gi.exe
-value-          -field description-
0x80000 (512k)   Minimum amount of stack space (bytes/K/M)
0x4000 (16k)     Size of real-memory transfer buffer (bytes/K/M)
ginstall         Base name of file to actually run (max 8 chars, ""=self)
""               Value to pass as file component of argv[0] (max 16 chars, 
""=default)
CWSDPMI.EXE      Program to load to provide DPMI services (if needed)

The only differences I see are in the case of the executable name
(`GINSTALL' vs `ginstall') and in the minimum stack size (256k vs
512k).  But, even when I create a symlink to `ginstall' using the
uppercase name and the smaller stack size, it will work and the
original `install' symlink does not!  In fact, any symlink I create
will work as expected, but `install' will not.  What's going on?