public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "textdirected at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66534] Compilation error of gfortran building on YDL6.2 Date: Sun, 06 Sep 2015 08:08:00 -0000 [thread overview] Message-ID: <bug-66534-4-Y8Ie6Kb9Yk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66534-4@http.gcc.gnu.org/bugzilla/> 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
next prev parent reply other threads:[~2015-09-06 8:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-14 11:13 [Bug fortran/66534] New: " textdirected at gmail dot com 2015-06-14 11:33 ` [Bug fortran/66534] " schwab@linux-m68k.org 2015-08-30 10:42 ` dominiq at lps dot ens.fr 2015-09-06 8:08 ` textdirected at gmail dot com [this message] 2015-10-10 8:48 ` dominiq at lps dot ens.fr 2015-10-15 5:29 ` textdirected at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-66534-4-Y8Ie6Kb9Yk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).