public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "multya at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60953] New: configure: error: GNU Fortran is not working
Date: Thu, 24 Apr 2014 14:03:00 -0000	[thread overview]
Message-ID: <bug-60953-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60953
           Summary: configure: error: GNU Fortran is not working
           Product: gcc
           Version: 4.7.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: multya at outlook dot com

Created attachment 32676
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32676&action=edit
config.log

checking whether the GNU Fortran compiler is working... no
configure: error: GNU Fortran is not working; please report a bug in
http://gcc.gnu.org/bugzilla, attaching
/usr/ports/lang/gcc/work/build/i386-portbld-freebsd8.1/libgfortran/config.log
gmake[1]: *** [configure-target-libgfortran] Error 1
gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build'


             reply	other threads:[~2014-04-24 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 14:03 multya at outlook dot com [this message]
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
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@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).