public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danp57 at optonline dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29292] configure produces strange gmp, mpfr lib directories.
Date: Thu, 12 Oct 2006 23:43:00 -0000 [thread overview]
Message-ID: <20061012234253.7872.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29292-13225@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from danp57 at optonline dot net 2006-10-12 23:42 -------
Subject: Re: configure produces strange gmp,
mpfr lib directories.
Thank you very much for the question! It never occurred to me to use/
force 32-bit. Configure worked smoothly. I did do a build of C,
which doesn't need gmp and mpfr, thinking that some of the confusion
could have been due to odd library re-directions due to the placement
of a back-level gcc in a non-standard place (the machine I'm using
mounted it elsewhere). I'm now using the 4.1.1 to build this with,
with 32 bit selected. Other headaches: ulimit.
Another comment: I WISH I could tell you it fixed the problem... but
I will not be able to know for a few days. The "checking for...
usability, presence" stuff takes forever... much longer than much
more modest machines (like my wife's old laptop running cygwin).
You'll just have to wait a day or so to find out how this went!
Dan
On Oct 12, 2006, at 12:58 PM, dje at gcc dot gnu dot org wrote:
>
>
> ------- Comment #4 from dje at gcc dot gnu dot org 2006-10-12
> 16:58 -------
> You should be using
>
> --with-gmp=/usr/local
>
> Are you sure that /usr/local/lib/libgmp.a exists and was built
> correct? Use
> static libraries and make sure that you are building 32-bit libgmp
> and libmpfr.
>
>
> --
>
> dje at gcc dot gnu dot org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------
> ------
> CC| |dje at gcc dot gnu
> dot org
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29292
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29292
next prev parent reply other threads:[~2006-10-12 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 23:07 [Bug fortran/29292] New: " danp57 at optonline dot net
2006-09-30 1:56 ` [Bug target/29292] " kargl at gcc dot gnu dot org
2006-09-30 23:28 ` pinskia at gcc dot gnu dot org
2006-10-02 21:02 ` danp57 at optonline dot net
2006-10-12 16:59 ` dje at gcc dot gnu dot org
2006-10-12 23:43 ` danp57 at optonline dot net [this message]
2006-10-12 23:46 ` pinskia at gcc dot gnu dot org
2006-10-13 0:00 ` dje at gcc dot gnu dot org
2006-10-13 0:26 ` danp57 at optonline dot net
2006-10-13 1:33 ` danp57 at optonline dot net
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=20061012234253.7872.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).