This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Using gcc 3.3.3


Thanks
I tried building 3.3.3 using 3.3.1, which didn't work when doing 'make
bootstrap'. But then I did a successful 'make bootstrap' of 3.3.2 using
3.3.1. The bootstrapped 3.3.2 works fine, and claims to have been compiled
by itself not 3.3.1. Even -mno-cygwin works fine on it. So I'm now happy, in
that I've used my 'on-a-plate' compiler to compile myself a better one. But
I'm greedy and curious, I want more. So now I've included in the path
environment variable the path to this before the cygwin path, and I'm now
trying to make bootstrap 3.3.3 using 3.3.2. Do you think it should work?
When I type 'man patch' it says 'no manual entry for patch', do I have to
install this extra?

And what of this Chris geezer, does he have a known email address? Can he be
contacted to be asked questions such as this?



> -----Original Message-----
> From: Larry Hall [mailto:cygwin-lh@cygwin.com]
> Sent: 15 March 2004 02:11
> To: Ben Taylor; Cygwin List
> Subject: RE: Using gcc 3.3.3
>
>
> 'man patch'.
>
> But according to Chris, who knows more about Cygwin's gcc than I do,
> -mno-cygwin should be configurable with vanilla gcc sources.  So, if
> you're having difficulty with your locally built gcc/g++, you'll
> need to figure out what's different in your environment.
>
> Larry
>
>
> At 03:58 PM 3/14/2004, you wrote:
> >How do I apply patches to my existing Cygwin installation?
> >
> >
> >> -----Original Message-----
> >> From: Larry Hall [mailto:cygwin-lh@cygwin.com]
> >> Sent: 14 March 2004 18:59
> >> To: Ben Taylor; cygwin@cygwin.com
> >> Subject: Re: Using gcc 3.3.3
> >>
> >>
> >> At 09:50 AM 3/14/2004, you wrote:
> >> >Hi
> >> >
> >> >I have got Cygwin running on my windows XP pc, using gcc 3.3.1.
> >> I downloaded
> >> >gcc 3.3.3 release, and managed to build it, however when I tried
> >> to compile
> >> >a windows application using it it compiled ok but gave a linker error
> >> >'couldn't find crt2.o'. It gave this error when I was trying
> to compile
> >> >with -mno-cygwin, which worked with gcc 3.3.1. I found that this
> >> file was in
> >> >c:/cygwin/lib/mingw, but passing an option on to the linker such
> >> >as -Wl,"-Lc:/cygwin/lib/mingw" or other variations on this
> didn't work.
> >> >However when I copied the crt2.o file to c:/cygwin/lib, it
> >> worked! But then
> >> >I read that -mno-cygwin wasn't  included on gcc 3.3.3. So was
> >> this a fluke?
> >> >Or is there a standard way to use gcc 3.3.3 on cygwin?
> >> >
> >> >Also if I used g++ 3.3.3 to compile but g++ 3.3.1 that came with
> >> cygwin to
> >> >link, it also works fine! Is it then actually using the benefits
> >> of the more
> >> >modern version?
> >>
> >>
> >> The gcc compiler suite for Cygwin contains patches to include the
> >> '-mno-cygwin' switch.  Since gcc 3.3.3 isn't part of the Cygwin
> >> distribution yet, you would need to patch your local version if
> >> you want this functionality prior to it's inclusion in Cygwin.
>



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]