change in glibc-2.10: use #define __USE_XOPEN2K8 instead of #define __USE_GNU .
Created attachment 192821 [details, diff]
patch for telepathy-idle to build with glibc-2.10
Should the __USE_GNU still be changed to _GNU_SOURCE? (This is way out of my gnu-c league, but everyone seems to be stating that __USE_GNU is somehow evil and _GNU_SOURCE should be used instead -- and that's what actually happens, e.g., in src/idle-muc-channel.c, but not elsewhere in the code.)
Same problem here, still not fixed in the portage tree :\
I just kept the __USE_GNU as it is, since it used to compile fine with < glibc-2.10. So this workaround (patch) should do with all glibc.
Upstream(?) seems to have this kind of patch:
fixed, thanks (not used the attached patch but the one from upstream bug)
The fix is also needed for 0.1.4. Upstream did not fix this bug until nearly a month after 0.1.4's release.
From http://git.collabora.co.uk/?p=telepathy-idle.git (and edited a bit)
Define _GNU_SOURCE not __USE_GNU to get strnlen(3).
version 0.1.4 telepathy-idle-0.1.4