X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <004701c8323d$c0da8780$6501a8c0 AT paul> Subject: RE: cygwin 1.5.24-2 gcc 3.4.4 stdio.h Date: Thu, 29 Nov 2007 10:42:10 -0000 Message-ID: <014a01c83274$7eb2a090$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <004701c8323d$c0da8780$6501a8c0@paul> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 29 November 2007 04:10, Paul Edwards wrote: > until I ran across this C compiler that > doesn't even manage to conform to a spec that has been available for > around 20 years. I get what you're asking for, and it's perfectly reasonable, but it's just not the compiler's problem. The C compiler does conform; it's the newlib C *run-time library* that is not C89-compatible. Gcc is doing it's part, but gcc does not supply stdio.h; it's up to the library to wrap the headers in #ifdef. > Which list do I need to go to to consult someone > about modifying newlib? I can probably make the changes to get it at least > closer to C89 compliance if I have someone to give patches to. The newlib home page is http://sourceware.org/newlib. There's a newlib@ mailing list hosted at sourceware, and that's where to send patches; the home page has all the usual details of cvs access etc. and how to contribute. I'm sure your help would be welcomed! cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/