Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <418123AD.2060402@agilent.com> Date: Thu, 28 Oct 2004 09:51:58 -0700 From: Earl Chew User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Revised precompiled header support on cygwin References: <41802878 DOT 8070208 AT agilent DOT com> <20041028013026 DOT GA5371 AT trixie DOT casa DOT cgf DOT cx> <41807E89 DOT 3050103 AT agilent DOT com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Oct 2004 16:52:02.0790 (UTC) FILETIME=[72E33060:01C4BD0E] Brian Ford wrote: > Does any of this help you understand where CGF is coming from? Brian, Thanks for taking the time to explain the situation to me. I'm not sure what I'll do at this point. I think this is a worthwhile patch in general. The precompiled header processing in gcc is a valuable feature to be able to use. I can understand the reasons to avoid cygwin local patches. Unfortunately some of the host-*.c details changed between 3.4.1 and 3.4.2, and right now I'm using 3.4.1. I suspect submitting the 3.4.1 based patches to the gcc mainainers won't cut it because they're past that point. I suppose this will have to wait until I can find the opportunity to move to 3.4.2 --- or later. Earl -- 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/