public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51103] configure: error: GNU Fortran is not working
Date: Sat, 12 Nov 2011 17:25:00 -0000	[thread overview]
Message-ID: <bug-51103-4-vhLkPeXwW7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51103-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-11-12 16:52:37 UTC ---
On Sat, Nov 12, 2011 at 02:51:32PM +0000, richalewis at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51103
> 
> --- Comment #7 from Richard Lewis <richalewis at gmail dot com> 2011-11-12 14:51:32 UTC ---
> Created attachment 25807
>   --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25807
> libgfortran build log
> 
> -- 

In what directory is the gcc source code?

In what directory did you run configure?


  parent reply	other threads:[~2011-11-12 16:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12  6:31 [Bug fortran/51103] New: " richalewis at gmail dot com
2011-11-12  6:40 ` [Bug fortran/51103] " kargl at gcc dot gnu.org
2011-11-12  7:20 ` richalewis at gmail dot com
2011-11-12  8:33 ` richalewis at gmail dot com
2011-11-12 10:10 ` kargl at gcc dot gnu.org
2011-11-12 11:13 ` richalewis at gmail dot com
2011-11-12 14:07 ` janus at gcc dot gnu.org
2011-11-12 16:01 ` richalewis at gmail dot com
2011-11-12 17:25 ` sgk at troutmask dot apl.washington.edu [this message]
2011-11-12 17:30 ` richalewis at gmail dot com
2011-11-12 17:54 ` richalewis at gmail dot com
2011-11-12 17:55 ` sgk at troutmask dot apl.washington.edu
2011-11-12 17:58 ` richalewis at gmail dot com
2011-11-12 19:10 ` sgk at troutmask dot apl.washington.edu
2011-11-13  0:48 ` fxcoudert at gcc dot gnu.org
2011-12-15  0:50 ` pinskia at gcc dot gnu.org
2011-12-19 23:40 ` pinskia 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-51103-4-vhLkPeXwW7@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).