Message-Id: <m112b44-0000BJC@sloep108.cs.vu.nl>
Date:     Fri, 9 Jul 99 15:51:43 MET DST
From: Michel de Ruiter  <mdruiter AT cs DOT vu DOT nl>
To: djgpp-workers AT delorie DOT com
Subject:  DJGPP cvs and gcc-2.95
Reply-To: djgpp-workers AT delorie DOT com

Dear workers,

I have tried to compile the current DJGPP cvs libsource, with gcc-2.95
(as compiled by Andris IIRC).

Trying that, gcc crashed twice, on unlzw.c and redir.c. I am currently
investigating the reason, which is difficult as the crashes only
happen *some* of the times, not always. It may be my computer, as I
have new SIMMs and an other motherboard.

Also, I have some questions about the current libsource:

- There are 8 filenames ending in .orig in manifest/djlsr202.mft. I
  realize the *203.mft have not been created yet, so the *.orig will
  not be in them. True?
- I remember having discussed a patch (proposed by me :-) to
  src/libc/dos/io/setmode.c, so setting a tty to O_BINARY would at
  least give an interruptible situation. Is the situation fixed, in
  some other way, or do we want to leave the situation as is (at least
  for 2.03)?
- src/libc/dos/io/setmode.txh discusses to some length the possibility
  to read the console in binary mode. Is there any situation where
  this could be useful? And, as the input is line buffered,
  __djgpp_set_ctrl_c will not really help to generate signals, will
  it? Or do I still miss something, about console in binary mode?

During compiling, gcc issued the following warnings. I have not had
the time to "correct" them (yet). Someone else might?

dbgcom.c:25: warning: `id' defined but not used
fullscr.c: In function `redraw':
fullscr.c:1618: warning: long double format, double arg (arg 3)
stubify.c: In function `coff2exe':
stubify.c:50: warning: `used_temp' might be used uninitialized in this function
scheck.c: In function `scheck':
scheck.c:56: warning: cast discards qualifiers from pointer target type

Groente, Michel.