From: pavenis AT lanet DOT lv
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Date: Sat, 27 May 2000 19:05:13 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: GDB 5.0 is released
Message-ID: <39301C69.19430.D639E6@localhost>
In-reply-to: <200005271434.RAA15393@alpha.netvision.net.il>
References: <slrn8iuqtp DOT h2 DOT drososa AT localhost DOT localdomain>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 27 May 2000, at 17:34, Eli Zaretskii wrote:

> Here's your problem: your DOS/Windows directory appears on your PATH
> before the DJGPP's bin subdirectory, so Bash is picking the stock
> FIND.EXE instead of the Gnu Find utility.  Microsoft's FIND.EXE is an
> incompatible program, so it complains about what seems to it as wrong
> arguments.
> 
> A solution is either rearrange your PATH or rename the stock FIND.EXE
> to something else (or even remove it, since it's worthless if you have
> GNU Grep installed).
> 
> After you correct this, I suggest to remove the entire GDB source tree
> and unpack it again, then configure and build it anew.
> 
> Thanks for reporting this, I will see how to make the installation
> process more robust.

It's perhaps rather common problem. So why not to add to djconfig.sh
something similar to following:

case x`find --version 2>&1 | sed -e 's/[ ]/_/g'` in
        xFIND:_Para*) echo M$ FIND detected. Please get rid of it; exit 1;;
        xGNU_find*) ;;
        *) echo no GNU FIND found. Please install; exit 1;;
esac

Andris