From: "Rupert Wood" <me@rupey.net>
To: "'Martin Krischik'" <krischik@users.sourceforge.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: GCC does not build gfortran !!
Date: Fri, 07 Dec 2007 15:33:00 -0000 [thread overview]
Message-ID: <2c5501c838e6$6ee4efb0$4caecf10$@net> (raw)
In-Reply-To: <20071207162437.2vor9b2qpwosgkk0@server265-han.de-nserver.de>
Martin Krischik wrote:
> Here an except from my latest Solaris compile:
:
> /opt/gnat/gcc/bin/ld: skipping incompatible
> /opt/gnat/gcc/lib/libgmp.so when searching for -lgmp
The issue on Solaris is that GMP defaults to building a 64-bit library even when the rest of your toolchain is 32-bit. Force GMP to build as 32-bit and it should work; I think you can do this by passing --host=sparc-sun-solaris2.10 (i.e. not sparc64) to configure.
Rup.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next prev parent reply other threads:[~2007-12-07 15:33 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 [this message]
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='2c5501c838e6$6ee4efb0$4caecf10$@net' \
--to=me@rupey.net \
--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).