This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: (new) Failure building GFortran (Cygwin)
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Angelo Graziosi'" <angelo dot graziosi at alice dot it>, "'Paul Richard Thomas'" <paul dot richard dot thomas at gmail dot com>
- Cc: <fortran at gcc dot gnu dot org>, <gcc at gcc dot gnu dot org>
- Date: Sun, 6 Jul 2008 21:59:38 +0100
- Subject: RE: (new) Failure building GFortran (Cygwin)
- References: <486629E7.7030003@alice.it> <339c37f20806281308y78981c25h22fec3bddb77d60b@mail.gmail.com> <486F57D8.6060400@alice.it>
Angelo Graziosi wrote on 05 July 2008 12:16:
> For the sake of completeness I want to flag that the current snapshot
> 4.4-20080704 has new failures:
> /work/gcc/gcc/ggc-page.c -o ggc-page.o
> cc1: warnings being treated as errors
> /work/gcc/gcc/ggc-page.c: In function 'alloc_page':
> /work/gcc/gcc/ggc-page.c:802: error: request for implicit conversion
> from 'void *' to 'char *' not permitted in C++
> /work/gcc/gcc/ggc-page.c:845: error: request for implicit conversion
> from 'void *' to 'struct page_entry *' not permitted in C++
> make[3]: *** [ggc-page.o] Error 1
> But I am confused in any case: Why 'not permitted in C++'?
> Isn't xgcc a C compiler?
>
> I am enabling only C,Fortran!
This is probably fallout from Kaveh's current work on making sure gcc
stays c++ compatible. Your patch looked good to me, you should send it with
a ChangeLog to gcc-patches.
cheers,
DaveK
--
Can't think of a witty .sigline today....