mpn/gcd_1.asm fails to build on Solaris 10 SPARC 64bit with Studio 12.3 cc - SOLVED

Mark Ashley mark at
Wed May 8 23:49:21 CEST 2013

I can appreciate the nuances in GMP, it's not obvious though to casual
builders such as myself what it needs (and doesn't need), hence the point
of this discussion and putting it into the archives for google to find
later. I'd have found it very useful three days ago :)

Because my GMP packages will be downloaded and used by tens of thousands of
others I might re-compile with ABI=64, --disable-assembly for SPARC and
--enable-fat for x86, thereby providing the widest possible platform
support. Speed isn't a big factor, portability is. Let me know if that
seems outrageous.

On Thu, May 9, 2013 at 2:37 AM, Torbjorn Granlund <tg at> wrote:

> Mark Ashley <mark at> writes:
>   I use setenv CC "cc -xtarget=ultra -m64 -xcode=pic32" as my compiler for
> all of
>   my Solaris packages on SPARC 64bit. It's a very widely used default for
> the
>   Solaris Studio compiler. My Solaris Package Archive (
>   pub/packages/solaris/sparc/index.html ) has used that for thousands of
>   packages. It's why I was surprised to see issues compiling GMP, though
> as the
>   blurb says, it does tend to exercise compilers in ways most programs
> don't, due
>   to the assembler code I suspect.
> For good and for bad, GMP's configure wants to be tld what to do (use
> this and that ABI, build static lib or shared lib or both, etc), it does
> not like to be given options and then try to figure out what the user
> might have in mind.
> Forcing pic options onto a plain GMP build is just plain and simply
> wrong; they will then be used for both static and shared lib.
>   * p.s. if the documented way is to compile with gcc then that's an issue
> as I
>   never ever use it.
> That's recommended, but we do support any reasonable command-line
> compiler.
> --
> Torbjörn

More information about the gmp-bugs mailing list