Re: Problem with gcc 3.4.4-1 and -mno-cygwin switch

["Gerrit P. Haase" <gerrit at familiehaase dot de>]

David Rothenberger wrote:

> On 6/9/2005 12:24 PM, David Rothenberger wrote:
>
> > On 6/9/2005 12:17 PM, Gerrit P. Haase wrote:
> >
> > > David Rothenberger wrote:
> > >
> > > > % cygcheck -cv | grep gcc
> > > > Empty package gcc
> > > > gcc                     3.4.4-1              OK
> > > > gcc-core                3.4.4-1              OK
> > > > gcc-g++                 3.4.4-1              OK
> > > > Empty package gcc-mingw
> > > > gcc-mingw               20040810-1           OK
> > > > gcc-mingw-core          20040810-1           OK
> > > > gcc-mingw-g++           20040810-1           OK
> > > >
> > > > Same issue with test versions of gcc-mingw* packages.
> > >
> > >
> > >
> > >
> > > Many thanks.
> > >
> > > You're missing the gcc-mingw-* packages.
> >
> >
> >
> > Huh? Which gcc-mingw-* packages am I missing? See the output from 
> > cygcheck pasted above. Also, note that gcc -mno-cygwin works fine for 
> > me with gcc 3.3.3-1.
>
>
> Oh, I'm sorry. I think I see. There are some gcc-mingw-* packages after 
> 20040822-1 that fix the problem?

Yes.  And I suggest that you get a gold star because you found the first
mistake I made when building and uploading this package even before an
announcement was sent;)


Gerrit
--
=^..^=

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