Jonathan Dieter wrote: > For reference, you can find zck.h.in (which gets processed into zck.h > with the version added) at: > https://github.com/zchunk/zchunk/blob/master/include/zck.h.in > > and zck_private.h at: > https://github.com/zchunk/zchunk/blob/master/src/lib/zck_private.h > > As far as I can see, gcc-4.7 doesn't like that I'm typedefing the same > struct to the same type twice. Later versions don't see it as a > problem at all. > > (Just to be clear, this still happens if I change zck_private.h to say: > typedef struct zckCtx zckCtx;) IMHO, zck_private.h should #include "zck.h" and only define itself whatever is not defined in the public header. Kevin Kofler _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
