On 2018-02-11 19:21:33 -0500, Jeffrey Walton wrote:
> That's not true. In fact, Stallman specifically tells the project to
> adds the flags it needs. Below is from Section 7.2.3 of
> https://www.gnu.org/prep/standards/standards.html. This would fix the
> ARM compile problem, too:
> If there are C compiler options that must be used for proper
> compilation of certain files, do not include them in CFLAGS. Users
> expect to be able to specify CFLAGS freely themselves. Instead,
> arrange to pass the necessary options to the C compiler independently
> of CFLAGS, by writing them explicitly in the compilation commands or
> by defining an implicit rule, like this:

As written above, this is for C compilers. But GMP also has assembler
code. So, you need to provide an option that will affect the assembler
code. This is what ABI is for.

That said, perhaps GMP might be improved to detect the ABI by a
simple parsing of $CFLAGS when provided by the user (in case values
like -m32 or -m64 are standard). The reason is that the user could
have a generic CFLAGS for various software, while AFAIK, ABI is
specific to GMP.

Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
gmp-bugs mailing list

Reply via email to