[Bug fortran/59862] New: Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[Bug fortran/59862] New: Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[carlos.a.cruz at nasa dot gov]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

            Bug ID: 59862
           Summary: Code does not compile with 4.8.1 tarball release but
                    compiles with 4.8.1 SVN release
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: carlos.a.cruz at nasa dot gov

I have been attempting to compile a fortran code
(https://sourceforge.net/projects/pfunit/) on a Linux system running Red Hat
4.6.3-2 OS.

When compiling using a tarball release, i.e.:

wget http://ftp.gnu.org/gnu/gcc/gcc-4.8.1/gcc-4.8.1.tar.gz

the code fails with a compilation error that suggest that the compiler release
does not yet have a particular enhancement.

When compiling with an SVN release, i.e.

svn checkout svn://gcc.gnu.org/svn/gcc/tags/gcc_4_8_1_release

the code compiles just fine.

In both cases I installed the compiler using the same configure options.

This suggests that the tarball and SVN releases, at least gfortran, are not
identical.

[Bug fortran/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2014-01-17
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I have compiled the code with gfortran 4.8.2 built through fink from the
archive at ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.8.2/gcc-4.8.2.tar.bz2.

What is the "compilation error that suggest that the compiler release does not
yet have a particular enhancement"?

[Bug fortran/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[carlos.a.cruz at nasa dot gov]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

--- Comment #2 from Carlos A. Cruz <carlos.a.cruz at nasa dot gov> ---
I get the following error message:

SurrogateTestCase.F90:54.57:
         class (SurrogateTestCase), intent(inout) :: this
                                                        1
Error: Deferred-length character component 'getname' at (1) is not yet
supported

Note that pFUnit does compile with release 4.8.2 as well as 4.8.1. The issue I
am reporting here is that the 4.8.1 tarball and the 4.8.1 SVN distributions did
not work the same for me.

Thanks.

(In reply to Dominique d'Humieres from comment #1)
> I have compiled the code with gfortran 4.8.2 built through fink from the
> archive at ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.8.2/gcc-4.8.2.tar.bz2.
> 
> What is the "compilation error that suggest that the compiler release does
> not yet have a particular enhancement"?

[Bug fortran/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Can you make a diff of /path_tar/gcc/fortran and /path_svn/gcc/fortran?

The error

Error: Deferred-length character component 'getname' at (1) is not yet
supported

is still active even on trunk (4.9.0, r206729). The 4.8 (including 4.8.1 svn)
and 4.9 manual says

Deferred-length character strings of Fortran 2003 supports part of
the features of @code{ISO_VARYING_STRING} and should be considered as
replacement. (Namely, allocatable or pointers of the type
@code{character(len=:)}.)

[Bug other/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org
          Component|fortran                     |other

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I have downloaded the two releases. Comparing gcc/fortran, the only difference
is

Only in gcc-4.8.1/gcc/fortran/: gfortran.info

in wget http://ftp.gnu.org/gnu/gcc/gcc-4.8.1/gcc-4.8.1.tar.gz

Comparing gcc, the only difference is

Only in gcc-4.8.1/gcc/: gengtype-lex.c

I don't know if the presence or not of gengtype-lex.c can explain what you
report.
IMO this is a packaging issue not a gfortran one. I'ld like to close it as
WONTFIX, but I am CCing release managers for advice.

[Bug other/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #4)
> I have downloaded the two releases. Comparing gcc/fortran, the only
> difference is
> 
> Only in gcc-4.8.1/gcc/fortran/: gfortran.info
> 
> in wget http://ftp.gnu.org/gnu/gcc/gcc-4.8.1/gcc-4.8.1.tar.gz
> 
> Comparing gcc, the only difference is
> 
> Only in gcc-4.8.1/gcc/: gengtype-lex.c
> 
> I don't know if the presence or not of gengtype-lex.c can explain what you
> report.
> IMO this is a packaging issue not a gfortran one. I'ld like to close it as
> WONTFIX, but I am CCing release managers for advice.

The release tarball contain generated files so you don't need tools like
flex or makeinfo to build GCC.  Those are not present in SVN, so this is
definitely not a packaging bug.

[Bug other/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59862

--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> The release tarball contain generated files so you don't need tools like
> flex or makeinfo to build GCC.  Those are not present in SVN, so this is
> definitely not a packaging bug.

Not sure to understand: gcc/gengtype-lex.c is in the tarball, but not in SVN.
>From the above I understand that gcc/gengtype-lex.c should also not be in the
tarball.
Is this correct? What could be the effect of gcc/gengtype-lex.c?