public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Krischik <krischik@users.sourceforge.net>
To: gcc-help@gcc.gnu.org
Subject: GMP and MPFR (Was: GCC does not build gfortran !!)
Date: Sat, 08 Dec 2007 08:03:00 -0000	[thread overview]
Message-ID: <200712080902.41508.krischik@users.sourceforge.net> (raw)
In-Reply-To: <m3tzmuqyws.fsf@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]

Am Freitag 07 Dezember 2007 schrieb Ian Lance Taylor:

> Martin Krischik <krischik@users.sourceforge.net> writes:
> > 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.
>
> Note that in gcc 4.3, all languages will require GMP and MPFR, not
> just Fortran.

That is extremely bad news for anybody trying to create GCC on a 
non-mainstream (i.E. Linux) platform.

Honestly: It took our team [1] month to create a working GCC/Ada for MinGW and 
it is still not repeatable (as in: change version number start script and 
done).

Making GMP and MPFR a prerequisite is a mistake! The GMP team with there need 
for speed made creating GMP a pain in the arse. See my other post on this 
thread. I created GMP but the resulting lib is worthless. Unproven best guess 
why: a 64 bit lib where a 32 bit lib is needed.

And expect an outcry son. Why? Well have a look at my build script:

	if test -e "%{Prefix}/lib/libgmp.so"  &&
	   test -e "%{Prefix}/lib/libmpfr.so" ;
	then
		Enables="--enable-gmp --enable-mpfr"
		Languages="${Languages},fortran";
	fi;

And another thing just struck me: We from the Ada community use cross 
compilers for embedded targets a lot. Targets which might not even have an 
operating system. How is this supposed to work in future?

Or not quite a drastic: Cross compiling on Windows for VMS. Do GMP and MPFR 
cross compile for VMS. Do they compile for VMS at all. Or for Symbian to name 
a new and hip OS for contrast.

You are going to loose many mon mainstream or cross compile platforms that 
way - they will stay with 4.2.x which will be at least "createable" for there 
needs. And all this all for some multi precision stuff which most people 
won't need. I at at least know more GCC users using exotic targets then MP 
math.

Martin

[1] http://gnuada.sf.net

-- 
Martin Krischik
mailto://krischik@users.sourceforge.net

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2007-12-08  8:03 UTC|newest]

Thread overview: 17+ 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
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         ` Martin Krischik [this message]
2007-12-08  8:11           ` GMP and MPFR (Was: GCC does not build gfortran !!) 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

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=200712080902.41508.krischik@users.sourceforge.net \
    --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).