Date:	Sun, 29 Aug 1999 14:50:57 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Maurice Lombardi <Maurice DOT Lombardi AT ujf-grenoble DOT fr>
cc:	djgpp AT delorie DOT com
Subject:	Re: bug in ginstall under bash ?
In-Reply-To:	<37C760AF.CF2EAB6A@ujf-grenoble.fr>
Message-ID:	<Pine.SUN.3.91.990829145038.9438v-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 27 Aug 1999, Maurice Lombardi wrote:

> SHELL = /bin/sh
> 
> all:
>         /bin/ginstall -c anyfile anydir ;
> ----------------------------------------
> 
> If I don't put the ; at the end of the last line make fails with a message:
> 
> /bin/ginstall -c anyfile anydir
> make.exe: *** [all] Error -1
> 
> with the ; included it is ok.

Do you actually have ginstall.exe in the /bin directory on the current
drive?

If not, then what you see is a feature, not a bug: Bash treats
/bin/foo pathnames specially, since many Unix scripts use them
unconditionally.  The semi-colon on the command line forces Make to
call the shell, and then it works.  Without the semi-colon, the
command is invoked directly by Make, and then it fails because there's
no /bin/ginstall.exe.

The correct solution is to configure the package so that INSTALL is
replaced with "${DJDIR}/bin/ginstall -c".  Then it will work
regardless.

- Raw text -