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:	<48F648E0 DOT 7040807 AT cornell DOT edu> <024801c92f1b$46bacec0$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48F6A9D5 DOT 20900 AT cornell DOT edu>
Subject:	RE: Headers not found when gcc4 installed without gcc3
Date:	Thu, 16 Oct 2008 10:31:06 +0100
Message-ID:	<02a001c92f71$ea5097d0$9601a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<48F6A9D5.20900@cornell.edu>
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

Ken Brown wrote on 16 October 2008 03:41:

> On 10/15/2008 7:10 PM, Dave Korn wrote:
>> there's no way on earth that installing Gcc-3 should
>> cause any X-related headers to be pulled in.  Both setup.hints for
>> gcc-core and gcc4-core pull in w32api, and that's it by the way of
>> headers. 
>> 
>>   Is it perhaps possible that your initial install failed to completely
>> run and the second time round setup.exe got the missing bits anyway -
>> only coincidentally at the same time as you installed gcc-core?
> 
> It's possible.  What puzzles me, though, is that the X11 headers were
> never missing; they were in /usr/X11R6/include all along.  [Maybe I
> didn't make that clear in my original post.]  It's just that those
> headers weren't found by the configure script.  So I thought that the
> installation of gcc-core might have done something to get the (already
> existing) headers into the search path for headers.  Is that impossible?

  Well, the main thing it would have done is make an executable called "gcc"
available in your $PATH, which could well solve any number of failures in a
configure script if by any chance you forgot to specify "CC=gcc-4 CXX=g++-4"
the first time you tried to configure it....



    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 -