Date:	Tue, 17 Sep 2002 20:59:28 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender:	pavenis AT ieva06
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Cc:	Andrew Cottrell <acottrel AT ihug DOT com DOT au>,
	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>, djgpp-workers AT delorie DOT com
Subject:	Re: V2.04 work list (was... status page)
In-Reply-To:	<10209171450.AA16719@clio.rice.edu>
Message-ID:	<Pine.A41.4.05.10209172048080.9364-100000@ieva06>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 17 Sep 2002, Charles Sandmann wrote:

> > > As far as I can tell from looking at mails in my todo folder, the only
> > > major issue is the one with rm on Windows 2k/XP. Plus lots of testing!
> 
> I don't really think that's quite true - we need to come up with a list of
> what's in - what's out - and discuss.  For example, something like making
> sure the library and headers are compliant with newer versions of the C
> standard.  What to do about iconv in packages.  The new malloc package.
> Image size (should we UPX the distributions?).  Dynamic linking of libc.
> Wide chars?  Compatibility with application distributions, etc ...

About UPX: I'm using it already for some time (binaries in last GCC and
binutils packages for DJGPP are compressed woth UPX). At least I haven't
heard too much objections.


Trying to build some days old GCC-3.3 CVS snapshot. Some of issues are
also djdev20X related:

default stack size (512k) is too small even for compiling C compiler.
So one cannot bootstrap it. I rebuild stub.asm after changing the default
to 1M and after that proceeded much more far. Perhaps we should consider
to either increase it (who knows when we'll need to increase it next
time?) or find some easy way how to change the default without rebuilding
stubify.exe or running stubedit.exe explicitly

More issues with building libstdc++-v3. Appears that linker script must
again be changed (fortunatelly I have put it in GCC distribution with name
djgpp-x.djl, but it seems that it will live there for a long time)	

Of course also absence of gdb521b.zip in Simtelnet. gdb-5.1.1 is unusable
with DWARF debug info generated by GCC-3.2 and 3.3

Andris

- Raw text -