| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
| List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
| List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
| Sender: | cygwin-owner AT sources DOT redhat DOT com |
| Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
| Message-ID: | <80575AFA5F0DD31197CE00805F650D7602CDEA@wilber.adroit.com> |
| From: | "Robinow, David" <drobinow AT dayton DOT adroit DOT com> |
| To: | cygwin AT sourceware DOT cygnus DOT com |
| Subject: | RE: [Beginner] Parsing errors compiling headers |
| Date: | Thu, 26 Oct 2000 13:49:00 -0400 |
| MIME-Version: | 1.0 |
| X-Mailer: | Internet Mail Service (5.5.2650.21) |
> 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 cygwin-unsubscribe AT sourceware DOT cygnus DOT com
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |