Patch 0003 in Bug #685479 fixes this problem (but since it's 0003 and not 0001, it doesn't apply standalone.... should be easy enough to understand what's needed though).
It would probably be a good idea to get this patch to apply alone, so it can be included in the 0.16 series....

Created attachment 225964 [details] [review]
fix build

Created attachment 225965 [details] [review]
modules link needed libs

Created attachment 225966 [details] [review]
librygel-* links needed libs

the above patches apply on top of the rygel-0-16 branch (head at 76042d3e1e28ebfcd9bcc7666efa15fc8558385c). This makes rygel 0.16 build on top of a gupnp stack which has all pkg-config files modified to use Requires.private instead of Requires. Hopefully this will make sure rygel 0.16 builds on top of future versions of the gupnp stack (given that there are no other incompatibilities that prevent that).

It can't be build from vala against GUPnP 0.19. The GUPnP vapi is slightly incompatible because the old one contained a work-around for a work-around. There's a patch on master to change that, but I don't want to apply it to 0.16.

What's the difference of applying the old series of patches and the new one?

(In reply to comment #7)
> What's the difference of applying the old series of patches and the new one?

These patches are the same as "patch no. 3" from the other series made to apply against 0.16.... 

Given that the next major rygel update will be needed to build against next major gupnp versions and the patch series has already been applied there, I guess we can just close this bug as obsolete....

Well this only applies if building from vala, building the distributed tarball still works.