From: Martin Krischik <krischik@users.sourceforge.net>
To: gcc-help@gcc.gnu.org
Subject: Re: GCC does not build gfortran !!
Date: Fri, 07 Dec 2007 15:25:00 -0000 [thread overview]
Message-ID: <20071207162437.2vor9b2qpwosgkk0@server265-han.de-nserver.de> (raw)
In-Reply-To: <765852.6744.qm@web51303.mail.re2.yahoo.com>
Zitat von Sampath Koppole <sampathkoppole@yahoo.com>:
> Dear all,
> When I try to build my gcc (version 4.2.2) it does not
> build gfortran.
In the past The GNU Ada Project created Fortran just for the fun of it
- but we have given up on it - not because we don't like Fortran or
compiling Fortran is troublesome.
No it's because of GMP and MPFR. Fortran now needs those two libraries
to be installed. And those two are a real pain in the arse. If your
distribution hasn't got them I pity you.
Here an except from my latest Solaris compile:
----------------------------------------------------------
configure:23091: checking for __gmpz_init in -lgmp
configure:23121: /opt/gnat/gcc/bin/gcc -o conftest -Wall
-Wmissing-prototypes -g -O2 -I/opt/gnat/gcc/include
-L/opt/gnat/gcc/lib -L/opt/gnat/gcc/lib
-Wl,--library-path=/opt/gnat/gcc/lib
-Wl,--library-path=/usr/openwin/sfw/lib
-Wl,-rpath-link=/usr/openwin/sfw/lib
-Wl,--library-path=/usr/local/ssl/lib
-Wl,-rpath-link=/usr/local/ssl/lib -Wl,-rpath-link=/opt/gnat/gcc/lib
-Wl,--library-path=/opt/gnat/tools/lib
-Wl,-rpath-link=/opt/gnat/tools/lib conftest.c -lgmp >&5
/opt/gnat/gcc/bin/ld: skipping incompatible
/opt/gnat/gcc/lib/libgmp.so when searching for -lgmp
/opt/gnat/gcc/bin/ld: skipping incompatible
/opt/gnat/gcc/lib/libgmp.so when searching for -lgmp
/opt/gnat/gcc/bin/ld: skipping incompatible
/opt/gnat/gcc/lib/gcc/sparc-sun-solaris2.10/4.2.2/../../../libgmp.so
when searching for -lgmp
/opt/gnat/gcc/bin/ld: skipping incompatible
/opt/gnat/gcc/lib/libgmp.so when searching for -lgmp
/opt/gnat/gcc/bin/ld: skipping incompatible
/opt/gnat/gcc/lib/libgmp.so when searching for -lgmp
/opt/gnat/gcc/bin/ld: cannot find -lgmp
----------------------------------------------------------
And even if you manage to compile them both the trouble does not end.
No guarantee that GCC will like the freshly compiled libs. Not
dynamic, not at the right place - the list of problems is endless. I
regret the time I wasted on it.
In the past Ada was the most difficult language (self hosted - you
need a working Ada compiler to create the Ada compiler) - but now it's
Fortran with it's insistence on GMP and MPFR.
Martin
next prev parent reply other threads:[~2007-12-07 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 13:47 C Preprocessor for 64-bit Sampath Koppole
2007-11-28 18:43 ` 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 [this message]
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 8:03 ` GMP and MPFR (Was: GCC does not build gfortran !!) Martin Krischik
2007-12-08 8:11 ` Brian Dessent
2007-12-08 13:05 ` Martin Krischik
2007-12-08 19:27 ` Brian Dessent
2007-12-08 4:47 ` GCC does not build gfortran !! 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
2007-12-07 16:13 Timothy C Prince
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=20071207162437.2vor9b2qpwosgkk0@server265-han.de-nserver.de \
--to=krischik@users.sourceforge.net \
--cc=gcc-help@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).