www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/09/22/09:40:32

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <002e01c91c9b$30fb6460$4001a8c0 AT mycomputer> <5E25AF06EFB9EA4A87C19BC98F5C87530188805C AT core-email DOT int DOT ascribe DOT com> <002401c91cb2$677b2590$4001a8c0 AT mycomputer>
Subject: RE: g_assertions
Date: Mon, 22 Sep 2008 14:39:46 +0100
Message-ID: <003601c91cb8$ad265320$9601a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <002401c91cb2$677b2590$4001a8c0@mycomputer>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

John Emmas wrote on 22 September 2008 13:55:

> Thanks Phil,
> 
> That sounds very plausible but I'm not sure it's right in this case.  

  I'm pretty sure of it.  The only thing that can cause that compiler error is
characters between the backslash and the newline.

> I
> only have 2 copies of glib.h on my system and I'm pretty sure they came
> with the Cygwin installation.  I looked at both of them in a hex editor
> and they seem to have Unix style line-endings.

  I can't make your testcase compile here.  You didn't show the command line
but without some kind of -I option it's not going to even find glib.h, and
without you showing the command line we don't know which one or from where.

  The next step in investigating would be to compile it again, adding the
"--save-temps" flag, so you get a copy of the preprocessed output in a .i
file.  Then check /that/ for EOLs of the wrong type, maybe using something
like

tail -20 *.i | od -c

and looking out for "\r"s.  (I chose "-20" as a guess, just to get the
pre-processed version of my_func and skip out most of the #include headers and
other irrelevancies that end up in the preprocessed output).

    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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019