public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: "Martin Krischik" <krischik@users.sourceforge.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC does not build gfortran !!
Date: Wed, 19 Dec 2007 20:06:00 -0000	[thread overview]
Message-ID: <b609cb3b0712191206q768ac65bu1411cb9048851a9e@mail.gmail.com> (raw)
In-Reply-To: <200712192034.23093.krischik@users.sourceforge.net>

On 12/19/07, Martin Krischik <krischik@users.sourceforge.net> wrote:
> Am Samstag 08 Dezember 2007 schrieb NightStrike:
>
> > If you put the gmp and mpfr source in subdirectories of the gcc tree,
> > gcc will build them automatically for you and you don't have to worry
> > about anything. I do this on 5 different build platforms, and it
> > works superbly.
> >
> > You can put this in a script:
> >
> > cd gcc
> >
> > wget -qO- ftp://ftp.gnu.org/gnu/gmp/gmp-4.2.2.tar.bz2 | tar xjf - &&
> > mv gmp-4.2.2 gmp
> >
> > wget -qO- http://www.mpfr.org/mpfr-current/mpfr-2.3.0.tar.bz2 | tar
> > xjf - && mv mpfr-2.3.0 mpfr
> >
> >
> > The rest is seemless. You don't even need to use the --with-gmp and
> > --with-mpfr options. It's wonderful.
>
> I finally found some to time to try it. Only - ./configure still tested the
> pre installed version of gmp and failed. Since I am not root I can't remove
> the pre installed version. So another dead end in the battle with gmp / mpfr.
>
> It think that when GCC 4.3.0 goes live this group will be swamped with gmp /
> mpfr related posts. Mark my word.

This is the part in configure.ac that you are trying to trigger:

if test "x$with_mpfr$with_mpfr_include$with_mpfr_lib" = x && test -d
${srcdir}/mpfr; then
  gmplibs='-L$$r/$(HOST_SUBDIR)/mpfr/.libs
-L$$r/$(HOST_SUBDIR)/mpfr/_libs '"$gmplibs"
  gmpinc='-I$$r/$(HOST_SUBDIR)/mpfr -I$$s/mpfr '"$gmpinc"
  # Do not test the mpfr version.  Assume that it is sufficient, since
  # it is in the source tree, and the library has not been built yet
  # but it would be included on the link line in the version check below
  # hence making the test fail.
  have_gmp=yes
fi

And similarly with gmp.

Are you sure that you put the gmp and mpfr directories in the right
place?  ie, $(srcdir)/gmp?

  reply	other threads:[~2007-12-19 20:06 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
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 [this message]
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=b609cb3b0712191206q768ac65bu1411cb9048851a9e@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=krischik@users.sourceforge.net \
    /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).