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/49438] error during make
Date: Thu, 16 Jun 2011 16:32:00 -0000 [thread overview]
Message-ID: <bug-49438-4-YmJyBhS49Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49438-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49438
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org 2011-06-16 16:31:23 UTC ---
(In reply to comment #0)
> Created attachment 24545 [details]
> config.log
>
> make ends with
>
> 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
> /home/e.ab/software/src/gcc-4.5.3-build/i686-pc-linux-gnu/libgfortran/config.log
> make[1]: *** [configure-target-libgfortran] Error 1
> make[1]: Leaving directory `/data1/software/src/gcc-4.5.3-build'
> make: *** [all] Error 2
>
What is the configure command line you used to configure
the gcc?
next prev parent reply other threads:[~2011-06-16 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 12:53 [Bug fortran/49438] New: " eisoab at gmail dot com
2011-06-16 13:40 ` [Bug fortran/49438] " burnus at gcc dot gnu.org
2011-06-16 16:32 ` kargl at gcc dot gnu.org [this message]
2011-06-16 17:36 ` eisoab at gmail dot com
2011-06-16 17:53 ` sgk at troutmask dot apl.washington.edu
2011-06-16 17:57 ` eisoab at gmail dot com
2011-06-16 18:08 ` eisoab at gmail dot com
2011-07-24 18:42 ` dfranke at gcc dot gnu.org
2011-11-07 22:48 ` fxcoudert at gcc dot gnu.org
2011-11-07 22:53 ` fxcoudert 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-49438-4-YmJyBhS49Z@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).