X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	"'Lloyd Wood'" <L DOT Wood AT surrey DOT ac DOT uk>,
	"'Chris Elliott'" <cl3ellio AT interchange DOT ubc DOT ca>
Cc:	<cygwin AT cygwin DOT com>, <geomview-users AT lists DOT sourceforge DOT net>,
	<geomview-devel AT lists DOT sourceforge DOT net>
Subject:	RE: Geomview & Cygwin setup
Date:	Fri, 28 Apr 2006 15:11:21 +0100
Message-ID:	<008b01c66acd$a08616e0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<7.0.1.0.0.20060428142922.05995e40@surrey.ac.uk>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On 28 April 2006 14:35, Lloyd Wood wrote:

> __CYGWIN__ is still valid under gcc version 3.4.4 (cygming special),
> as this test shows:

  You really need to read some manuals, as you wouldn't have to do things like
this if you had read about the -dM option.  (You also wouldn't have led
yourself up the garden path about mingw if you had read about -mno-cygwin).
Hint:

 gcc -dM -E - < /dev/null

> (Why #define says __CYGWIN__ and gcc -v says something else is
> silly.) 

  No it isn't.  Your assumption that the two have to be in some way related is
silly.  As is attempting to parse the output from "gcc -v" to detect a given
target rather than using one of the predefined macros, which is what they are
for and how it is supposed to be done.  The output from "gcc -v" is for
*humans* to read, and version strings are allowed to have free-format text and
no guarantees are provided regarding the content or formatting of that text or
how it may or may not change in the future.

>I suspect something has changed affecting the CYGWIN test in glob.c

  First you said that __CYGWIN__ is still valid.  Then you think that
something has changed affecting the '#ifdef __CYGWIN__' test in glob.c.  Since
you acknowledge that __CYGWIN__ is still valid, presumably you believe that
#ifdef has been changed to only succeed if a symbol is not defined?

  Now, if you stop posting random guesses and uninformed speculation and try
and tell us what the actual *problem* is, perhaps we can answer some questions
for you about the recent changes to d_ino under cygwin?


    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 -