From: "Timothy C Prince" <tprince@myrealbox.com>
To: sampathkoppole@yahoo.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC does not build gfortran !!
Date: Fri, 07 Dec 2007 16:13:00 -0000 [thread overview]
Message-ID: <1197044006.c7dcd97ctprince@myrealbox.com> (raw)
-----Original Message-----
From: Sampath Koppole <sampathkoppole@yahoo.com>
To: gcc-help@gcc.gnu.org
Date: Fri, 7 Dec 2007 06:10:12 -0800 (PST)
Subject: GCC does not build gfortran !!
Dear all,
When I try to build my gcc (version 4.2.2) it does not
build gfortran.
when I run:
.../gcc-4.2.2/configure --prefix=/usr/prog/gcc
--enable-languages=all
I get the follwing config.log file:
checking for any version of mpfr.h... no
The following languages will be built: c,c++,java,objc
*** This configuration is not supported in the
following subdirectories:
target-libada gnattools target-libgfortran
(Any other directories should still work fine.)
____________
You need that header. It should be installed with the development version of mpfr libraries. It's easy enough to build and install mpfr from source, if you aren't sure of finding the right version. I too miss the point of having mpfr builds with and without mpfr.h.
Tim Prince
next reply other threads:[~2007-12-07 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 16:13 Timothy C Prince [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-28 18:43 C Preprocessor for 64-bit Ian Lance Taylor
2007-12-07 14:10 ` GCC does not build gfortran !! Sampath Koppole
2007-12-07 15:14 ` Rupert Wood
2007-12-07 15:25 ` Martin Krischik
2007-12-07 15:33 ` Rupert Wood
2007-12-08 8:03 ` Martin Krischik
2007-12-07 15:59 ` Ian Lance Taylor
2007-12-08 4:47 ` NightStrike
2007-12-08 9:04 ` Martin Krischik
2007-12-11 16:20 ` NightStrike
2007-12-19 19:39 ` Martin Krischik
2007-12-19 20:06 ` NightStrike
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=1197044006.c7dcd97ctprince@myrealbox.com \
--to=tprince@myrealbox.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sampathkoppole@yahoo.com \
--cc=tprince@computer.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).