See 1541. Something got screwed up in the somewhat bizarre chain of includes. My
only work around is to manually include the needed typedefs.

I'm vaguely surprised you were able to recompile libgcrypt 1.5.3 using Xcode 5.0.

See 1540.

It has been mentioned at the ML that your problems might be related to a
misconfigured build machine. Please continue discussion at the ML.

@balderdash: Using --disable-agent is not a good idea

The --disable-agent doesn't matter for this bug. It's the same without it.

It's an artifact from Homebrew, which for whatever reason splits things into one
package for just the agent, and another for gnupg2-sans-agent.

Something got screwed up in the somewhat bizarre chain of includes. My

only work around is to manually include the needed typedefs.

I'm not a programmer and I don't know what "manually include the needed
typedefs" means.

Interestingly the problem I report doesn't exist when gnupg2 is built within
Homebrew.

Well, I don't known what Homebrew is?

Homebrew is an OSX package manager.

It's interesting that it built inside Homebrew, because they do some automatic
adjustment of CFLAGS etc. to make a package more likely to build on OSX.

Probably what happened is they removed a flag which is causing the problem I'm
reporting, but only on XCode5.0

I'm no programmer, but I'll look into this further.

Thus this is a bug in homebrew and not in GnuPG. If you have a solution please
post it here for reference.

Homebrew is the only way building with Xcode5 can SUCCEED. Building the "normal"
way, with ./configure --stuff && make, FAILS. The bug is in gnupg2. Homebrew has
somehow stepped around the bug.

Then please describe the error building GnuPG using the one and only way -
everything else is not supported.

Then please describe the error building GnuPG using the one and only way -

everything else is not supported.

??? I *did*, in this very bug report right here, in my original post. Is my
attachment not viewable?

Oh sorry. It is not readily viewable in the browser due to the MIME type.

This issue has already been discussed on the mailing list and another bug
report. Your problem is a messed up toolchain installation. We can't do
anything about that. If you want to follow up on this, please do so on the
mailing list. The audience of the bug tracker is too small and we don't have
any OSX stuff here for testing.