Re: FORTRAN GCC 4.3.X library

[Takis Psarogiannakopoulos <takis at XFree86 dot Org>]

Thomas,

Thank you for your answer. I didnt email the fortran list cause I thought
its not worth it. I was under the impression I was missing something
something very obvious.
You are right its the -std=c99 that is needed and the const restrict seems
to be the old __restrict right? I must confess thats a very peculiar
name... I have never use it really but i kind rememebr a regression about
that name.
I am using a gcc-4.3.x/config/mh-os file that picks up all the flags and
as this file by default in GCC is being copied "as is" to the main
Makefile can it override all the flags.
-std=gnu99 is defined on libgfortran/Makefile.in/am AM_CFLAGS with other
warnings. As have switched the warnings off from the main config/mh-*
config file the flag -std=gnu99 is not passed to the compile flags.
However the main Makefile has a -D_GNU_SOURCE clearly defined and its
there really it should also have included the -std=gnu99 flag.
Maybe someone can do that change?
If a system doesnt need a -std=gnu99 there is not harm, but if its needed
and its not there the whole compilation fail!

Kind Regards,


On Wed, 4 Mar 2009, Thomas Koenig wrote:

> On Wed, 2009-03-04 at 09:05 -0800, Takis Psarogiannakopoulos wrote:
>
> Hi Takis,
>
> a general point: It is probably better to mail fortran@gcc.gnu.org
> directly, instead of individual developers.  This is more likely to
> generate a useful response, or a useful discussion :-)  I've CC:'d my
> reply there.
>
> > I am dealing with the gcc 4.3.x sources in a new port and I have a small
> > issue with libgfortan :
> >
> > In gcc-4.3.x/libgfrotran/generated all fuction arguments seem to have a
> >
> > const restrict
> >
> > prefix. My compilation fails due to that no defined. What it should be and
> > where it should be defined?
>
> This is standard C99.  Libgfortran is supposed to be compiled with
> -std=gnu99, and it is also supposed to be built by the recently built
> gcc/gfortran.  You can check for -std=gnu99 in the generated Makefile.
> If this isn't happening, there is an error in the build machinery for
> your system.  Could you maybe supply us with some more details?
>
> 	Thomas
>