GnuPG 2.1.3 Fails to Compile OS X

[Dominyk Tiller]

Hi Ethan,

Thanks for the quick replies today, appreciate those.

You're correct on GNU's GCC, in that it compiles successfully. It looks
like I labelled one of my Clang compiles "GCC_Comp1.txt" last night
accidentally and looked for the error rather than double checking the
compiler to make sure I'd actually labelled the output correctly. Lesson
learned there.

The Clang error on all three platforms examined, 10.8, 10.9 & 10.10
remains true. I double checked that just to make sure I wasn't being an
idiot there as well.

Thanks for the offer of the signed, pre-build tarball. That was kind of
you. Sadly in this case it wouldn't have helped because I'm trying to
update our Homebrew/Versions GnuPG21 package. I'm still using the 2.0.x
branch personally, for now.

Is the Clang error something GnuPG can fix in the coming versions or are
we going to be waiting on Apple to fix the underlying LLVM issue?

Apologies for my mess up on the GCC failure, and Thanks for the help.
Appreciated!

Dom

Sent from OS X. If you wish to communicate more securely my PGP Public
Key is 0x872524db9d74326c.

On 12/04/2015 23:00, Ethan Sherriff wrote:
> Sorry didn't see what you said about the error occuring with GNU GCC,
> what version are you using? On OS X Yosemite 10.10.3 (Latest Public Beta
> 14D131, XCode 6.3 6D570), with GNU GCC 4.9.2 installed from source,
> gnupg-2.1.3 builds fine.
> ------------------------------------------------------------------------
> From: Dominyk Tiller <mailto:dominyktiller at gmail.com>
> Sent: ‎12/‎04/‎2015 21:01
> To: gnupg-users at gnupg.org <mailto:gnupg-users at gnupg.org>
> Subject: GnuPG 2.1.3 Fails to Compile OS X
> 
> Hey Werner,
> 
> Thanks for the new release!
> 
> I'm having some issues making it compile on OS X, right across
> 10.8-10.10.3. Tried both Apple's Clang and GNU's GCC so I'm presuming
> the error isn't compiler-specific.
> 
> It's throwing slightly different errors on OS X 10.8 than it is on 10.9
> and 10.10. The 10.8 error is:
> 
> =========================================================
> t-stringhelp.c:488:3: error: function definition is not allowed here
>   {
>   ^
> t-stringhelp.c:536:4: error: expected ';' at end of declaration
>   }
>    ^
>    ;
> 2 errors generated.
> make[3]: *** [t-stringhelp.o] Error 1
> =========================================================
> 
> 
> 
> And the 10.9 - 10.10.3 error is just:
> 
> =========================================================
> t-stringhelp.c:488:3: error: function definition is not allowed here
>   {
>   ^
> 1 error generated.
> make[3]: *** [t-stringhelp.o] Error 1
> =========================================================
> 
> Have attached various compile logs.
> 
> Cheers,
> 
> Dom
> 
> -- 
> Sent from OS X. If you wish to communicate more securely my PGP Public
> Key is 0x872524db9d74326c.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20150413/adff872e/attachment-0001.sig>