From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76550 invoked by alias); 6 Sep 2015 08:08:58 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 76507 invoked by uid 48); 6 Sep 2015 08:08:51 -0000 From: "textdirected at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: textdirected at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg00438.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534 --- Comment #4 from HEMMI, Shigeru --- 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