From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32191 invoked by alias); 10 Dec 2012 08:41:52 -0000 Received: (qmail 32132 invoked by uid 48); 10 Dec 2012 08:41:37 -0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/55601] libgfortran build fails with --disable-libquadmath Date: Mon, 10 Dec 2012 08:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-12/txt/msg00927.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55601 --- Comment #2 from Tobias Burnus 2012-12-10 08:41:36 UTC --- Hmm, seemingly, the check ignores --disable-libquadmath-support by only testing for C's __float support, cf. libgfortran/acinclude.m4's LIBGFOR_CHECK_FLOAT128. gfortran itself is checked via libgfortran/acinclude.m4's LIBGFOR_WORKING_GFORTRAN. One probably should augment the C test by a Fortran "REAL(16)" test. Additionally, one could directly honour --disable-libquadmath-support, which I think is also passed to libgfortran's configure. Regarding the --disable-libquadmath combined with --enable-libquadmath-support: Some warning would be useful, but the question is how to trigger it.