> If I knew which list to send email to I would try to prevail > on the gcc/cpp owner You are the gcc/cpp owner (sort of) > to fix the problem. Apparently, it sees > LF > CRLF > ok, and > \LF > ok, but > \CRLF > gets broken. It seems like an easy fix. That way people > wouldn't have to worry about > the exact format of header files in /usr/include. If it's so easy why don't you fix it yourself? -- Want to unsubscribe from this list? Send a message to [EMAIL PROTECTED]
- [Beginner] Parsing errors compiling headers Paulius Bulotas
- Re: [Beginner] Parsing errors compilin... Larry Hall (RFK Partners, Inc)
- Re: [Beginner] Parsing errors compilin... Ed Bradford/Raleigh/IBM
- Re: [Beginner] Parsing errors comp... Matt Minnis
- Re: [Beginner] Parsing errors compilin... Ed Bradford/Raleigh/IBM
- New GCC test release available Christopher Faylor
- RE: [Beginner] Parsing errors compilin... Robinow, David
- RE: [Beginner] Parsing errors compilin... Ed Bradford/Raleigh/IBM