Use of the __GMP_CC and __GMP_CFLAGS macros

Emmanuel Thomé emmanuel.thome at
Thu Oct 4 08:47:58 CEST 2012

Just adding my 2 cents.

I have the impression that the exporting of these variables to gmp.h
causes gmp to mandate that the build environment has to match the one
of the user (which _uses_ gmp  to compile something else), in that if
some compiler has been used for building gmp, then surely specifying
the command line to it has implications regarding the PATH, not to
mention possibly the exact compiler version itself.

I understand the motivations behind these flags. Certainly guessing
which abi was selected, and how to select it, is no picnic. But the
requirement above seems somewhat bogus. Am I understanding correctly
that under Debian, the build environment reaches the C compiler
through a bizarre path, which never matches the one on user machines ?
I am not sure Debian is really to blame for that.



On Thu, Oct 4, 2012 at 8:08 AM, Torbjorn Granlund <tg at> wrote:
> "Steve M. Robbins" <steve at> writes:
>   Dear Torbjorn: if you had followed the discussion, you would see that Debian
>   is not adding complication.  Debian is building the packages exactly according
>   to the gmp process.
> But then why isn't it working for the exact intended purpose of these
> macos?  We want these macros to be useful for their purpose, right?
> If documentation that leaves room for misunderstanding is the reason
> behind the current situation, then I would be glad to clarify it.
> --
> Torbjörn
> _______________________________________________
> gmp-discuss mailing list
> gmp-discuss at

More information about the gmp-discuss mailing list