Message-ID: <3E68E3E7.AEEDAA3C@yahoo.com> From: CBFalconer Organization: Ched Research X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: Compiling GRX 245 References: <002101c2e3fc$181e0700$0300a8c0 AT rivasaiicfa DOT com DOT ar> <3E67AEC5 DOT 9AF3CA27 AT yahoo DOT com> <200303062110 DOT h26LAJD32316 AT envy DOT delorie DOT com> <3E6879B8 DOT 92765D5A AT phekda DOT freeserve DOT co DOT uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 26 Date: Fri, 07 Mar 2003 18:44:41 GMT NNTP-Posting-Host: 12.90.169.71 X-Complaints-To: abuse AT worldnet DOT att DOT net X-Trace: bgtnsc04-news.ops.worldnet.att.net 1047062681 12.90.169.71 (Fri, 07 Mar 2003 18:44:41 GMT) NNTP-Posting-Date: Fri, 07 Mar 2003 18:44:41 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Richard Dawe wrote: > DJ Delorie wrote: > > > > > Out of perverse curiosity I did just that, and found nothing in > > > any of the read*.* files that mentioned va_list. > > > > Perhaps it's covered by this phrase in readme.DJGPP: > > > > DJGPP-2.03 and above (Please verify that You really have current > > update of djdev203.zip if You use 2.03). > > > > IIRC we fixed the header file in the 2.03 update. > > Yes, it was fixed in DJGPP 2.03 refresh 2. You know that, I suspected it, but how did anyone expect the readmes (which don't mention va_list) to clue the OP (who mentioned va_list) in? Maybe a release should contain some sort of summary of bugs fixed. -- Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net) Available for consulting/temporary embedded and systems. USE worldnet address!