Mail Archives: djgpp-workers/2001/01/09/09:30:44
On Tue, Jan 09, 2001 at 01:04:53AM -0500, Mark E. wrote:
> Hello Laurynas,
> I think I have a fix for the seemingly random occurance of inappropriate
> arguments being passed to the programs xgcc calls. It works for me. Let me
> know if it works for you.
Thanks! It really helped. Please submit it to GCC ASAP.
BTW, GCC is going to branch for 3.0 release on Jan 14, and
there is still a lot of DJGPP work to do. I will do what
I can, but I have my exams on this week too. What a fine
coincidence :-(.
And here is my todo:
1) Top priority: libstdc++-v3 port. I've patched libtool,
and created necessarry config and autobuild files. It still
does not build, but I'll try to fix it ASAP.
2) Top priority: xvalloc: currently it wastes twice the
allocated memory. This means windows users can use only
32MB for GCC. Not too good, to say the least. Zack Weinberg
(GCC developer) was working on this, but I'm not sure
if it will make it to official 3.0. But I think we will
have to add DJGPP-specific patches anyway for DJGPP release.
3) Configure/build scripts - it would be best to do without
them, by proper defines in config/mh-djgpp, configure.in
etc. etc.
4) Building without LFN - djunpack.bat from GDB should be
made general, make a list of SFN names for unpacking, sedding
makefile and here we go.
5) Other than C++ runtime libs....
6) ???
- Raw text -