From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Fri, 14 Apr 2000 17:02:47 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: gdb-20000402
Message-ID: <38F74F37.11714.7CBDC8@localhost>
References: <Pine DOT A41 DOT 4 DOT 05 DOT 10004041913550 DOT 11930-100000 AT ieva05 DOT lanet DOT lv>
In-reply-to: <Pine.SUN.3.91.1000405113910.20661L-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

On 5 Apr 2000, at 11:39, Eli Zaretskii wrote:

> 
> On Tue, 4 Apr 2000, Andris Pavenis wrote:
> 
> > 	./configure 	--build=i386-slackware-gnu \
> > 			--host=i586-pc-msdosdjgpp \
> > 			--target=i586-pc-msdosdjgpp \
> > 			--prefix=/dev/env/DJDIR \
> > 			--with-included-gettext
> 
> I suggest to lose --with-included-gettext: it won't work on
> DOS/Windows systems, since the encoding of non-ASCII characters is
> different.  Unless you recode the *.po and *.gmo files, of course.
> 
> I use --disable-nls instead.

Ok. It should be Ok. I even had to use --disable-nls under Linux to get
libgdb.a (and other libraries) usable to build rhide under Linux.

> 
> > I think it should build DJGPP binaries without problems now from original 
> > sources (only problem for me is that it's hard to use such build for
> > RHIDE)
> 
> The DJGPP configuration script does several things that are required
> for correct build.  Perhaps most of them are only relevant to non-LFN
> platfroms, I don't remember.

I mostly building either in DOS session under Win98 SE or under 
Linux. Perhaps I'll still use that way I'm building GDB for DJGPP as
I mostly interested in use it from RHIDE, not hacking GDB itself

However the next update of RHIDE will no more support using
GDB-4.18. So if one will want to compile it from sources he/she
will have to build GDB snapshot at first. Otherwise RHIDE seems
to work Ok with GDB snapshots (except rather broken binaries I had 
put on my web site for 2 days and removed after that, but these were 
RHIDE not GDB bugs)

Andris

PS. Currently I left building 12 April weekly snapshot of GDB. Let's 
see whether all will be Ok.