[Bug fortran/66534] New: Compilation error of gfortran building on YDL6.2

[Bug fortran/66534] New: Compilation error of gfortran building on YDL6.2

[textdirected at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

            Bug ID: 66534
           Summary: Compilation error of gfortran building on YDL6.2
           Product: gcc
           Version: 5.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: textdirected at gmail dot com
  Target Milestone: ---

Hello all,

When I tried to build gcc 5.0 downloaded from a mirror site, I encountered a
compilation error in building gfortran. I am working on YDL(yellow dog linux)
6.2 of an old iBook machine.

The console output is:

Checking multilib configuration for libgfortran...
make[2]: Entering directory `/home/zgzg/gcc-5.1.0/powerpc-unknown-linux
gnu/libgfortran'
make  all-am
make[3]: Entering directory
`/home/zgzg/gcc-5.1.0/powerpc-unknown-linux-gnu/libgfortran'
/bin/sh ./libtool  --tag=CC   --mode=compile
/home/zgzg/gcc-5.1.0/host-powerpc-unknown-linux-gnu/gcc/xgcc
-B/home/zgzg/gcc-5.1.0/host-powerpc-unknown-linux-gnu/gcc/
-B/opt/powerpc-unknown-linux-gnu/bin/ -B/opt/powerpc-unknown-linux-gnu/lib/
-isystem /opt/powerpc-unknown-linux-gnu/include -isystem
/opt/powerpc-unknown-linux-gnu/sys-include    -DHAVE_CONFIG_H -I.
-I../.././libgfortran  -iquote../.././libgfortran/io
-I../.././libgfortran/../gcc -I../.././libgfortran/../gcc/config 
-I../../host-powerpc-unknown-linux-gnu/gcc -I../.././libgfortran/../libgcc
-I../libgcc  -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wextra -Wwrite-strings
-Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules
-ffunction-sections -fdata-sections   -g -O2 -MT string.lo -MD -MP -MF
.deps/string.Tpo -c -o string.lo `test -f 'runtime/string.c' || echo
'../.././libgfortran/'`runtime/string.c
libtool: compile:  /home/zgzg/gcc-5.1.0/host-powerpc-unknown-linux-gnu/gcc/xgcc
-B/home/zgzg/gcc-5.1.0/host-powerpc-unknown-linux-gnu/gcc/
-B/opt/powerpc-unknown-linux-gnu/bin/ -B/opt/powerpc-unknown-linux-gnu/lib/
-isystem /opt/powerpc-unknown-linux-gnu/include -isystem
/opt/powerpc-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I.
-I../.././libgfortran -iquote../.././libgfortran/io
-I../.././libgfortran/../gcc -I../.././libgfortran/../gcc/config
-I../../host-powerpc-unknown-linux-gnu/gcc -I../.././libgfortran/../libgcc
-I../libgcc -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wextra -Wwrite-strings
-Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules
-ffunction-sections -fdata-sections -g -O2 -MT string.lo -MD -MP -MF
.deps/string.Tpo -c ../.././libgfortran/runtime/string.c  -fPIC -DPIC -o
.libs/string.o
make[3]: Leaving directory
`/home/zgzg/gcc-5.1.0/powerpc-unknown-linux-gnu/libgfortran'
make[2]: Leaving directory
`/home/zgzg/gcc-5.1.0/powerpc-unknown-linux-gnu/libgfortran'
make[1]: Leaving directory `/home/zgzg/gcc-5.1.0'
../.././libgfortran/runtime/string.c:96:1: error: static declaration of
'strnlen' follows non-static declaration
 strnlen (const char *s, size_t maxlen)
 ^
In file included from ../.././libgfortran/runtime/string.c:26:0:
/usr/include/string.h:249:15: note: previous declaration of 'strnlen' was here
 extern size_t strnlen (__const char *__string, size_t __maxlen)
               ^
In file included from /usr/include/string.h:417:0,
                 from ../.././libgfortran/runtime/string.c:26:
../.././libgfortran/runtime/string.c:110:1: error: expected identifier or '('
before '__extension__'
 strndup (const char *s, size_t n)
 ^
../.././libgfortran/runtime/string.c:96:1: warning: 'strnlen' defined but not
used [-Wunused-function]
 strnlen (const char *s, size_t maxlen)
 ^
make[3]: *** [string.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-target-libgfortran] Error 2
make: *** [all] Error 2

Please help me

best regards,

[Bug fortran/66534] Compilation error of gfortran building on YDL6.2

[schwab@linux-m68k.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-06-14
     Ever confirmed|0                           |1

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
Please attach the file
`/home/zgzg/gcc-5.1.0/powerpc-unknown-linux-gnu/libgfortran/config.log'.

[Bug fortran/66534] Compilation error of gfortran building on YDL6.2

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Created attachment 35780 [details]
> The file `/home/zgzg/gcc-5.1.0/powerpc-unknown-linux-gnu/libgfortran/config.log'

Are you sure you have posted the right log file?

I don't see the error

../.././libgfortran/runtime/string.c:96:1: error: static declaration of
'strnlen' 

in it and HAVE_STRNLEN is defined, thus the block

#ifndef HAVE_STRNLEN
static size_t
strnlen (const char *s, size_t maxlen)
{
  for (size_t ii = 0; ii < maxlen; ii++)
    {
      if (s[ii] == '\0')
        return ii;
    }
  return maxlen;
}
#endif

should be skipped.

[Bug fortran/66534] Compilation error of gfortran building on YDL6.2

[textdirected at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

--- Comment #4 from HEMMI, Shigeru <textdirected at gmail dot com> ---
Thanks for the reply. 

After my posting, i switched gfortran-5.1.0 to gfortran-5.2.0
expecting something improved. But the same bug has generated
at the same place.

Then i removed two blocks of libgfortran/runtime/string.c 
at your suggestion as shown below

#ifndef HAVE_STRNLEN
/* removed some lines */
#endif

#ifndef HAVE_STRNDUP
/* removed some lines */
#endif

As the result the error above not generated but I see the next bug (See below).
I am guessing many errors embedded for YDL 6.2, since
my hardware (Old iBook; Power PC G3 Processor) is very outdated,
probably nobody wishes to test it except me.

One option is that not to fix further bugs for Power PC G3 Processor 
to save developer's time. This option is OK for me because using
gfortran on my outdated hardware is not significant.
Another option is to continue bug fixing to improve gfortran sources.
Let me know which one is preferable for gfortran developers?


-------
FYI, the next encounterd bug is as follows:

make[2]: Entering directory
`/home/zgzg/libraries/gcc-5.2.0-build/powerpc-unknown-linux-gnu/libgfortran'
make  all-am
make[3]: Entering directory
`/home/zgzg/libraries/gcc-5.2.0-build/powerpc-unknown-linux-gnu/libgfortran'
/bin/sh ./libtool  --tag=CC   --mode=compile
/home/zgzg/libraries/gcc-5.2.0-build/./gcc/xgcc
-B/home/zgzg/libraries/gcc-5.2.0-build/./gcc/
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include    -DHAVE_CONFIG_H -I.
-I../../../gcc-5.2.0/libgfortran  -iquote../../../gcc-5.2.0/libgfortran/io
-I../../../gcc-5.2.0/libgfortran/../gcc
-I../../../gcc-5.2.0/libgfortran/../gcc/config  -I../.././gcc
-I../../../gcc-5.2.0/libgfortran/../libgcc -I../libgcc  -std=gnu11 -Wall
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra
-Wwrite-strings -Werror=implicit-function-declaration -Werror=vla
-fcx-fortran-rules -ffunction-sections -fdata-sections   -g -O2 -MT fpu.lo -MD
-MP -MF .deps/fpu.Tpo -c -o fpu.lo `test -f 'runtime/fpu.c' || echo
'../../../gcc-5.2.0/libgfortran/'`runtime/fpu.c
libtool: compile:  /home/zgzg/libraries/gcc-5.2.0-build/./gcc/xgcc
-B/home/zgzg/libraries/gcc-5.2.0-build/./gcc/
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I.
-I../../../gcc-5.2.0/libgfortran -iquote../../../gcc-5.2.0/libgfortran/io
-I../../../gcc-5.2.0/libgfortran/../gcc
-I../../../gcc-5.2.0/libgfortran/../gcc/config -I../.././gcc
-I../../../gcc-5.2.0/libgfortran/../libgcc -I../libgcc -std=gnu11 -Wall
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra
-Wwrite-strings -Werror=implicit-function-declaration -Werror=vla
-fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -MT fpu.lo -MD
-MP -MF .deps/fpu.Tpo -c ../../../gcc-5.2.0/libgfortran/runtime/fpu.c  -fPIC
-DPIC -o .libs/fpu.o
In file included from ../../../gcc-5.2.0/libgfortran/runtime/fpu.c:29:0:
./fpu-target.h:36:24: error: 'fenv_t' undeclared here (not in a function)
 _Static_assert (sizeof(fenv_t) <= (size_t) GFC_FPE_STATE_BUFFER_SIZE,
                        ^
./fpu-target.h:36:17: error: expression in static assertion is not an integer
 _Static_assert (sizeof(fenv_t) <= (size_t) GFC_FPE_STATE_BUFFER_SIZE,
                 ^
./fpu-target.h: In function 'get_fpu_except_flags':
./fpu-target.h:176:31: error: 'FE_ALL_EXCEPT' undeclared (first use in this
function)
   set_excepts = fetestexcept (FE_ALL_EXCEPT);
                               ^
./fpu-target.h:176:31: note: each undeclared identifier is reported only once
for each function it appears in
make[3]: *** [fpu.lo] Error 1
make[3]: Leaving directory
`/home/zgzg/libraries/gcc-5.2.0-build/powerpc-unknown-linux-gnu/libgfortran'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/zgzg/libraries/gcc-5.2.0-build/powerpc-unknown-linux-gnu/libgfortran'
make[1]: *** [all-target-libgfortran] Error 2
make[1]: Leaving directory `/home/zgzg/libraries/gcc-5.2.0-build'
make: *** [all] Error 2

[Bug fortran/66534] Compilation error of gfortran building on YDL6.2

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> As the result the error above not generated but I see the next bug (See below).
> I am guessing many errors embedded for YDL 6.2, since
> my hardware (Old iBook; Power PC G3 Processor) is very outdated,
> probably nobody wishes to test it except me.

Did you asked yellow dog linux for help?

> One option is that not to fix further bugs for Power PC G3 Processor 
> to save developer's time. This option is OK for me because using
> gfortran on my outdated hardware is not significant.
> Another option is to continue bug fixing to improve gfortran sources.
> Let me know which one is preferable for gfortran developers?

Well, gfortran is built on a quite broad range of platforms without the problem
you report. Unless you tackle the issue yourself, the problem will not be fixed
before the death of your G3! IMO it would be more honest to close this PR as
WONTFIX.

[Bug fortran/66534] Compilation error of gfortran building on YDL6.2

[textdirected at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534

--- Comment #6 from HEMMI, Shigeru <textdirected at gmail dot com> ---
Thanks for the reply.

> Did you asked yellow dog linux for help?
No, YDL seems stopping maintenance/developing.

> IMO it would be more honest to close this PR as WONTFIX.
I closed this thread at your suggestion.

> Well, gfortran is built on a quite broad range of platforms without the problem you report. 

My work is very much relying on gfortran.
I am using prebuilte gfortran binary (mingw-w64) mainly on Windows machine.
Almost all things going well.

Since gcc-5.2.0 gcc/g++ are built without problem on my outdated YDL machine,
so I expected gfortran is also well built on my YDL machine, but not.

Anyway, thank you very much for developing gfortran.

Best regards,