public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32289] mips version of gfortran produces internal compiler error
Date: Mon, 11 Jun 2007 19:09:00 -0000 [thread overview]
Message-ID: <20070611190857.15066.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32289-14284@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from kargl at gcc dot gnu dot org 2007-06-11 19:08 -------
(In reply to comment #2)
> I run Debian Linux 4.0 on my SGI box. When I type "apt-get source gcc-4.1", it
> downloads a version of gcc 4.1.2 that appears to be extensively hacked up. This
> version produced the referenced error. Could you tell me briefly where you get
> the source code, and what procedure you use to build the executable? Thank you
> very much.
Michael, I build gfortran from source, which for the mips architecture
is probably your only option. You'll need subversion. To get the bleeding
edge, do
cd tmp
svn checkout svn://gcc.gnu.org/svn/gcc/trunk
mkdir obj
cd obj
../trunk/configure --prefix=<path_to_install_to> --enable-languages=c,gfortran
make bootstrap
make install
You can also grab the gcc-4.2 tarball from ftp.gnu.org (or a mirror).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32289
next prev parent reply other threads:[~2007-06-11 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 16:52 [Bug fortran/32289] New: " michael dot a dot richmond at nasa dot gov
2007-06-11 18:16 ` [Bug fortran/32289] " kargl at gcc dot gnu dot org
2007-06-11 18:39 ` michael dot a dot richmond at nasa dot gov
2007-06-11 19:09 ` kargl at gcc dot gnu dot org [this message]
2007-06-12 11:22 ` tbm at cyrius dot com
2007-06-12 11:44 ` tbm at cyrius dot com
2007-06-12 14:04 ` michael dot a dot richmond at nasa dot gov
2007-06-12 14:13 ` tbm at cyrius dot com
2007-06-12 14:33 ` michael dot a dot richmond at nasa dot gov
2007-06-12 16:31 ` tbm at cyrius dot com
2007-06-13 20:49 ` fxcoudert at gcc dot gnu dot org
2007-06-14 12:00 ` tbm at cyrius dot com
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=20070611190857.15066.qmail@sourceware.org \
--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).