Date: Tue, 03 Oct 2000 18:21:11 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT inter DOT net DOT il
To: "Tim Van Holder" <tim DOT vanholder AT falconsoft DOT be>
Message-Id: <2110-Tue03Oct2000182111+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h
CC: djgpp AT delorie DOT com
In-reply-to: <fLiC5.53$WP5.3593@nreader1.kpnqwest.net>
	(tim DOT vanholder AT falconsoft DOT be)
Subject: Re: Building gdb 5.0
References: <200010020734 DOT JAA25254 AT bashir DOT belgium DOT eu DOT net> <8FC14D45F386sxmydejacom AT 130 DOT 133 DOT 1 DOT 4> <fLiC5.53$WP5 DOT 3593 AT nreader1 DOT kpnqwest DOT net>
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

> From: "Tim Van Holder" <tim DOT vanholder AT falconsoft DOT be>
> Newsgroups: comp.os.msdos.djgpp
> Date: Tue, 03 Oct 2000 10:43:23 GMT
>
> OK.
> Another possibility (though unlikely): the Cygnus configure may be expecting
> intl to be target-specific. Does it help if you create a i386-pc-msdosdjgpp/intl
> subdir in your build directory?

I doubt that this is the cause of the problem, since the script does
work when this same user on that same machine runs it from
COMMAND.COM's prompt, instead of from within Bash.

It must be something stupid, like some variable which Bash sets in an
interactive session, and the script somehow picks up.  (I never tried
to configure GDB from inside Bash.)

FWIW, when GDB is configured for DJGPP, it shouldn't even try to look
in the intl subdirectory, since GDB doesn't have NLS support yet.