public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47648] libgfortran/libgfortran.h:53:29: fatal error: quadmath_weak.h: No such f ile or directory - FreeBSD ia64
Date: Mon, 14 Feb 2011 21:02:00 -0000	[thread overview]
Message-ID: <bug-47648-4-xTpI5fPFMu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47648-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-02-14 20:56:26 UTC ---
Created attachment 23341
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23341
Possible libgfortran.dg/configure patch

The attached patch should allow to build libgfortran without
--disable-libquadmath-support. It does so by copying the check from
libquadmath.

I would be happy if someone could test this test on a machine where it failed
before.

(Note: A complimentary patch to support the missing bits on FreeBSD/ia64 would
be still useful.)


  parent reply	other threads:[~2011-02-14 20:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 17:37 [Bug fortran/47648] New: " mexas at bristol dot ac.uk
2011-02-09  7:43 ` [Bug fortran/47648] " burnus at gcc dot gnu.org
2011-02-13 10:12 ` burnus at gcc dot gnu.org
2011-02-14 21:02 ` burnus at gcc dot gnu.org [this message]
2011-02-15 21:31 ` burnus at gcc dot gnu.org
2011-02-22 11:06 ` [Bug fortran/47648] libgfortran/libgfortran.h:53:29: fatal error: quadmath_weak.h: No such file " burnus at gcc dot gnu.org
2014-03-22 19:45 ` dominiq at lps dot ens.fr
2015-09-05 10:37 ` dominiq at lps dot ens.fr

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-47648-4-xTpI5fPFMu@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: link
Be 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).