Re: gpgme 1.8 build failure (again)
> I am not sure whether this was helpful but I wrote That was the one I needed. :) For some reason, something in the GPGME build requires _DARWIN_C_SOURCE to be set. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpgme 1.8 build failure (again)
On Fri, 2 Dec 2016 07:05, r...@sixdemonbag.org said: > Unfortunately I didn't write this down, and the email thread is not in > the archive. (Only one message seems to be: The mails went to gnupg-devel and only one to gnupg-users. I am not sure whether this was helpful but I wrote We are still using x86_64-apple-darwin15.5.0 with ./configure --prefix=/Users/jenkins/prefix/native --enable-maintainer-mode 'CFLAGS= -D_DARWIN_C_SOURCE=90L -fPIC' 'CXXFLAGS= -D_DARWIN_C_SOURCE=90L -fPIC -std=c++11' and we see no problems. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. pgpZ_N5EPG1PA.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpgme 1.8 build failure (again)
Last month I had a build failure for GPGME 1.8 on macOS. I reported it to the list and received a useful answer about a custom preprocessor define that should've been, but was apparently was not, used. Unfortunately I didn't write this down, and the email thread is not in the archive. (Only one message seems to be: https://lists.gnupg.org/pipermail/gnupg-users/2016-November/057047.html ) Can anyone give me once again the magic invocation needed? Thanks. :) ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users