On domingo, 20 de novembro de 2016 19:51:53 PST Heldt-Sheller, Nathan wrote: > I ran into the same build issue yesterday. IoTivity 1.2.0 worked without > issues when it was released. But it looks like the update to TinyCBOR > since then has broken the 1.2.0 release.
As the TinyCBOR maintainer and the one who introduced the source-incompatible change, let me explain: the source-incompatible change was required in TinyCBOR to support building an application that uses a C89 strict compiler: the anonymous union that we used to use is not permitted then. I had the submitter wait several months between their pull request and the release of the change, so that other projects (IoTivity included) could adapt and not get broken. Let me also point out that I did fix IoTivity almost 4 months ago when we first introduced the breakage (see commit 3041fae14b358c51873b08967dc868080f47d819, dated July 30). Or at least I thought I had. The code that got broken was the security code, which was already there when I made that change. My guess? It wasn't enabled in my build because SECURE=0 is the default. So, sorry, but I wash my hands. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
