public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60953] configure: error: GNU Fortran is not working
Date: Fri, 25 Apr 2014 20:30:00 -0000 [thread overview]
Message-ID: <bug-60953-4-GNIyFvjd9l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60953-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60953
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to multya from comment #2)
> (In reply to Jakub Jelinek from comment #1)
> > Most likely a problem with your gmp or mpfr libraries.
>
> Gmp and mpfr was installed and reinstalled without any errors.
Have you tested your hardware? Do you have some artificially
low stack limt? Your config.log file shows
configure:12828: checking whether we are using the GNU Fortran compiler
configure:12841: /usr/ports/lang/gcc/work/build/./gcc/gfortran
-B/usr/ports/lang/gcc/work/build/./gcc/
-B/usr/local/i386-portbld-freebsd8.1/bin/
-B/usr/local/i386-portbld-freebsd8.1/lib/ -isystem
/usr/local/i386-portbld-freebsd8.1/include -isystem
/usr/local/i386-portbld-freebsd8.1/sys-include -c conftest.F >&5
<built-in>:0:0: internal compiler error: Segmentation fault: 11
This is often a sign of bad memory.
PS: I note that you appear to be using FreeBSD 8.1, which has an
end-of-life date July 31, 2012. You're obviously trying to install
from a recent FreeBSD ports collection snapshot. I doubt that it
has been tested on FreeBSD 8.1.
next prev parent reply other threads:[~2014-04-25 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 14:03 [Bug fortran/60953] New: " multya at outlook dot com
2014-04-24 14:24 ` [Bug fortran/60953] " jakub at gcc dot gnu.org
2014-04-25 20:30 ` kargl at gcc dot gnu.org [this message]
2014-05-09 14:06 ` dominiq at lps dot ens.fr
2014-08-01 8:25 ` multya at outlook dot com
2014-08-01 17:20 ` kargl at gcc dot gnu.org
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-60953-4-GNIyFvjd9l@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).