Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
To: cygwin AT cygwin DOT com
From: "Mikael" <mindcooler AT gmail DOT com>
Subject:  Re: I just tried to build GCC 4.0.0-RC2 on Cygwin
Date:  Wed, 20 Apr 2005 18:35:10 +0200
Lines: 50
Message-ID: <d4603k$er$1@sea.gmane.org>
References:  <d45run$fl9$1 AT sea DOT gmane DOT org> <SERRANO57DQzk7Q9KcN00000060 AT SERRANO DOT CAM DOT ARTIMI DOT COM>
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: 180.184.204.213.sol.worldonline.se
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-RFC2646: Format=Flowed; Original
X-IsSubscribed: yes


"Dave Korn" wrote:
> ----Original Message----
>>From: Mikael
>>Sent: 20 April 2005 16:24
>
>> As the topic says, I just tried to build the second release candidate of
>> GCC
>> 4.0.0 on Cygwin. The process itself was simple, but it took some time to
>> perform the make bootstrap part, but that was expected. All steps of the
>> build process completed successfully. I proceeded to try it on some of my
>> home-brewn programs and the tiny amount of testing I did was a success. 
>> Of
>> course -mno-cygwin doesn't work (it says: g++: installation problem,
>> cannot exec 'cc1plus': No such file or directory).
>> Apart from determining the proper configure options that should be used
>> for Cygwin (I probably didn't use them) and making -mno-cygwin work, what
>> else is required to port it fully to Cygwin?
>>
>> / M
>
>
>  Nothing really, although "making -mno-cygwin work" should be expanded to
> include "and applying all the other cyg-specific patches", but basically,
> that's all there is to it.

I seem to recall reading that the number of required patches for GCC has 
become less as GCC has been developed. I hope this is true so that porting 
4.0.* is easier than porting an earlier release.

>
>  Oh, and to find a good set of configure options, run "/bin/gcc -v", and
> your original cygwin gcc will spit out a list of the options it was
> configured with.
>

Yes, I was looking at those. I should've used ---enable-threads=posix for 
sure.

>
>    cheers,
>      DaveK
> -- 
> Can't think of a witty .sigline today....
>
>

/ M 




--
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/