[PATCH] mpi: Fix powerpc32 build

Dirk Eibach dirk.eibach at googlemail.com
Wed Apr 25 18:33:36 CEST 2018

Hi Werner,

Werner Koch <wk at gnupg.org> schrieb am Mi., 25. Apr. 2018, 17:54:

> On Wed, 25 Apr 2018 14:09, dirk.eibach at gdsys.cc said:
> > The ENTRY macro is called with C format parameter.
> > Adding a second underscore breaks the build.
> This code has not been changed for ages.  Thus I am wondering why you
> see a build problem only now.  Well, I can't remember that I ever used a
> powerpc32 box and this leads to the question why you start to use
> powerpc32 now.

We are using ppc32 for ages but require gcrypt just now.
I saw that the code has not been changed for ages. But if you have a look
at the assembler code it is pretty obvious that it cannot work this way:
both start the parameter with an underscore.
EALIGN adds another underscore while END does not.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20180425/fe1253ad/attachment.html>

More information about the Gcrypt-devel mailing list