public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jerin Joy" <jerinjoy@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: including MPFR and GMP
Date: Fri, 29 Aug 2008 20:11:00 -0000	[thread overview]
Message-ID: <c442cc490808271338u1922b3as3ad8e04196c8cdd2@mail.gmail.com> (raw)
In-Reply-To: <48B50DAC.CF190CD7@dessent.net>

Brian,

I had built the libraries but not run a make install because I didn't
have root access to the machine. The gcc configure was looking for the
'include' and 'lib' subdirectories for gmp and mpfr. I created a
softlink within the gmp and mpfr libs but gcc configure didn't like
it.

/import/dtg-data20/jj155244/tools/mpfr-2.3.1/include -> ../

Its working now that I ran a make install.

thanks,
Jerin

On Wed, Aug 27, 2008 at 1:17 AM, Brian Dessent <brian@dessent.net> wrote:
>
> Jerin Joy wrote:
>
> > configure: error: Building GCC requires GMP 4.1+ and MPFR 2.3.0+.
> > Try the --with-gmp and/or --with-mpfr options to specify their locations.
>
> Those options take the location where you installed the libraries, i.e.
> the --prefix that you gave when configuring them.
>
> > I don't know why it doesn't pick up the correct files from the path.
>
> The paths below look like the plain source dirs of an unpacked tarball.
> These options point to a built and installed copy of the libraries, not
> a bare source dir.
>
> > [jj155244@ gcc-4.3.0]$ ls -l /import/dtg-data20/jj155244/tools/mpfr-2.3.1  |less
> > total 7587
> > -rw-r-----    1 jj155244 wheel         755 Dec 31  2007 AUTHORS
> > -rw-r-----    1 jj155244 wheel        2915 Dec 31  2007 BUGS
> > -rw-r-----    1 jj155244 wheel       18013 Dec 31  2007 COPYING
> > -rw-r-----    1 jj155244 wheel       26440 Dec 31  2007 COPYING.LIB
> >
> > [jj155244@ gcc-4.3.0]$ ls -l /import/dtg-data20/jj155244/tools/gmp-4.2.3
> > total 4198
> > -rw-r-----    1 jj155244 wheel         843 Mar 22  2006 AUTHORS
> > -rw-r-----    1 jj155244 wheel       35147 Aug 30  2007 COPYING
> > -rw-r-----    1 jj155244 wheel        7639 Aug 30  2007 COPYING.LIB
> > -rw-r-----    1 jj155244 wheel      709734 Aug  2 13:54 ChangeLog
>
> It is also possible to have gcc bootstrap these libraries with itself,
> in the usual manner of a combined tree.
>
> Brian

      reply	other threads:[~2008-08-27 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 14:43 Jerin Joy
2008-08-27 20:39 ` Brian Dessent
2008-08-29 20:11   ` Jerin Joy [this message]

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=c442cc490808271338u1922b3as3ad8e04196c8cdd2@mail.gmail.com \
    --to=jerinjoy@gmail.com \
    --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).