public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mexas at bristol dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47648] New: libgfortran/libgfortran.h:53:29: fatal error: quadmath_weak.h: No such f ile or directory - FreeBSD ia64
Date: Tue, 08 Feb 2011 17:37:00 -0000 [thread overview]
Message-ID: <bug-47648-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47648
Summary: libgfortran/libgfortran.h:53:29: fatal error:
quadmath_weak.h: No such f ile or directory - FreeBSD
ia64
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: mexas@bristol.ac.uk
# uname -a
FreeBSD mech-cluster241.men.bris.ac.uk 9.0-CURRENT FreeBSD 9.0-CURRENT #1
r216732: Mon Dec 27 13:22:47 GMT 2010
root@mech-cluster241.men.bris.ac.uk:/usr/obj/usr/src/sys/TZAV ia64
#
Building gcc46 gives:
libtool: compile: /usr/ports/lang/gcc46/work/build/./gcc/xgcc
-B/usr/ports/lang/gcc46/work/build/./
gcc/ -B/usr/local/ia64-portbld-freebsd9.0/bin/
-B/usr/local/ia64-portbld-freebsd9.0/lib/ -isystem /u
sr/local/ia64-portbld-freebsd9.0/include -isystem
/usr/local/ia64-portbld-freebsd9.0/sys-include -DH
AVE_CONFIG_H -I. -I../.././../gcc-4.6-20110205/libgfortran
-iquote../.././../gcc-4.6-20110205/libgfo
rtran/io -I../.././../gcc-4.6-20110205/libgfortran/../gcc
-I../.././../gcc-4.6-20110205/libgfortran/
../gcc/config -I../.././gcc -D_GNU_SOURCE -std=gnu99 -Wall -Wstrict-prototypes
-Wmissing-prototypes
-Wold-style-definition -Wextra -Wwrite-strings -fcx-fortran-rules
-ffunction-sections -fdata-section
s -g -O2 -pipe -I/usr/local/include -fno-strict-aliasing -MT backtrace.lo -MD
-MP -MF .deps/backtrac
e.Tpo -c ../.././../gcc-4.6-20110205/libgfortran/runtime/backtrace.c -fPIC
-DPIC -o .libs/backtrace
.o
In file included from
../.././../gcc-4.6-20110205/libgfortran/runtime/backtrace.c:25:0:
../.././../gcc-4.6-20110205/libgfortran/libgfortran.h:53:29: fatal error:
quadmath_weak.h: No such file or directory
compilation terminated.
In file included from ../.././../gcc-4.6-20110205/libgfortran/fmain.c:4:0:
../.././../gcc-4.6-20110205/libgfortran/libgfortran.h:53:29: fatal error:
quadmath_weak.h: No such file or directory
compilation terminated.
gmake[3]: *** [fmain.lo] Error 1
gmake[3]: *** Waiting for unfinished jobs....
gmake[3]: *** [backtrace.lo] Error 1
gmake[3]: Leaving directory
`/usr/ports/lang/gcc46/work/build/ia64-portbld-freebsd9.0/libgfortran'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/lang/gcc46/work/build/ia64-portbld-freebsd9.0/libgfortran'
gmake[1]: *** [all-target-libgfortran] Error 2
gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build'
next reply other threads:[~2011-02-08 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 17:37 mexas at bristol dot ac.uk [this message]
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
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@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).