, Uze Choi
-Original Message-
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago Macieira
Sent: Thursday, November 24, 2016 2:43 AM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] 1.2.0 build failure
On ter?a-feira
Hi, everyone,
If there are any build issue remaining.
please file bugs and assign them to me,
I will try to sort them out or give hints on system I can't support.
Anyway a couple of comments, bellow
On 23/11/16 00:54, Nivedita Singhvi wrote:
> On 11/22/2016 03:39 PM, Thiago Macieira wrote:
>> O
On ter?a-feira, 22 de novembro de 2016 15:39:54 PST Nivedita Singhvi wrote:
> * It does not matter if it was working when first released, if 48hrs later
> is subsequently breaks with the existing code. And all subsequent
> users are affected going forward, for ever, as you point out, as it
On Nov 22, 2016 5:55 PM, "Nivedita Singhvi"
wrote:
>
> On 11/22/2016 03:39 PM, Thiago Macieira wrote:
>>
>> 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
On Nov 22, 2016 5:32 PM, "Thiago Macieira"
wrote:
>
> On domingo, 20 de novembro de 2016 13:55:57 PST Gregg Reynolds wrote:
> > wiki, yes. but more importantly, the downloads page. then again, the
> > message should say "don't bother downloading, it won't build". so why
not
> > just pull the d
or. (5.4.1
20160904)
-Original Message-
From: ??? (Uze Choi) [mailto:uzc...@samsung.com]
Sent: Tuesday, November 22, 2016 2:44 PM
To: 'maxi wu'; iotivity-dev at lists.iotivity.org
Subject: RE: [dev] 1.2.0 build failure
Hi Maxi,
Think about following example.
IoTivity next month rele
On 11/22/2016 03:39 PM, Thiago Macieira wrote:
> 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 brok
On ter?a-feira, 22 de novembro de 2016 16:08:05 PST maxi wu wrote:
> service/notification/cpp-wrapper/examples/linux/notificationserviceprovider.
> cpp:93:25: error: 'numeric_limits' was not declared in this scope
This was a simple case of missing #include. The code in question may have
built wit
Choi)'; iotivity-dev at lists.iotivity.org
Subject: RE: [dev] 1.2.0 build failure
Hi Choi,
I have to agree with Greg, something that is released should be built
without hacking/patching.
This problem could be fixed by modifying SCONS script, sure.
But I am very interested in the decision maki
On 11/22/2016 03:32 PM, Thiago Macieira wrote:
> On domingo, 20 de novembro de 2016 13:55:57 PST Gregg Reynolds wrote:
>> wiki, yes. but more importantly, the downloads page. then again, the
>> message should say "don't bother downloading, it won't build". so why not
>> just pull the downloads?
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 an
On domingo, 20 de novembro de 2016 13:55:57 PST Gregg Reynolds wrote:
> wiki, yes. but more importantly, the downloads page. then again, the
> message should say "don't bother downloading, it won't build". so why not
> just pull the downloads?
Open Source never, EVER removes or replaces a rele
On s?bado, 19 de novembro de 2016 15:25:48 PST Gregg Reynolds wrote:
> fwiw IMHO the 1.2.0 tarball should be pulled. it looks very bad to make an
> official release that doesn't even build!
It does build, just not with the current version of TinyCBOR. More to the
point, it did build with what wa
, 2016 1:45 PM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] 1.2.0 build failure
Hi Greg,
I believe most of these issues are from extlib library dependency.
Currently some of external library is referring the latest version which is
not originally allowed.
It happen due to the different
, 2016 8:50 AM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] 1.2.0 build failure
On 11/20/2016 03:57 PM, Nivedita Singhvi wrote:
> On 11/20/2016 11:51 AM, Heldt-Sheller, Nathan wrote:
>> Hi Gregg, Nivedita,
>>
>
> Thanks for the response, Nathan.
>
>> I
nolds' ; Nivedita Singhvi
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] 1.2.0 build failure
Hi Gregg, Nivedita,
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
Singhvi
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] 1.2.0 build failure
On Nov 19, 2016 4:29 PM, "Nivedita Singhvi" mailto:niveditasinghvi at gmail.com>> wrote:
>
> On 11/19/2016 12:56 PM, Kevin Kane via iotivity-dev wrote:
>>
>> This should h
On Nov 20, 2016 5:16 PM, "Nivedita Singhvi"
wrote:
>
> On 11/20/2016 02:57 PM, Nivedita Singhvi wrote:
>
>> The 1.1.1 release has broken for 3 months. Nothing on the download
>> page nor the Release Notes page indicates that it will not build (hence
>> the flow of user questions on -dev list):
>>
On 11/20/2016 03:57 PM, Nivedita Singhvi wrote:
> On 11/20/2016 11:51 AM, Heldt-Sheller, Nathan wrote:
>> Hi Gregg, Nivedita,
>>
>
> Thanks for the response, Nathan.
>
>> I ran into the same build issue yesterday. IoTivity 1.2.0 worked
>> without issues when it was released. But it looks like t
On 11/20/2016 02:57 PM, Nivedita Singhvi wrote:
> The 1.1.1 release has broken for 3 months. Nothing on the download
> page nor the Release Notes page indicates that it will not build (hence
> the flow of user questions on -dev list):
>
> https://www.iotivity.org/downloads/iotivity-1.1.1
> https:/
em.
> Thoughts?
>
> Thanks,
> Nathan
>
>
>
>
>
>
>
> *From:*iotivity-dev-bounces at lists.iotivity.org
> [mailto:iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Gregg
> Reynolds
> *Sent:* Saturday, November 19, 2016 2:34 PM
> *To:* Ni
On Nov 20, 2016 1:51 PM, "Heldt-Sheller, Nathan" <
nathan.heldt-sheller at intel.com> wrote:
>
> Hi Gregg, Nivedita,
>
>
>
> 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
fetch && git checkout
v0.3.2? to use the previous version of TinyCBOR.
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Gregg Reynolds
Sent: Saturday, November 19, 2016 11:52 AM
To: iotivity-dev
Subject: [dev] 1.2.0 build
>>
>>
>>
>> *From:*iotivity-dev-bounces at lists.iotivity.org
>> [mailto:iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Gregg
>> Reynolds
>> *Sent:* Saturday, November 19, 2016 11:52 AM
>> *To:* iotivity-dev
>> *Subject:* [dev] 1.2.
On Nov 19, 2016 4:06 PM, "Nivedita Singhvi"
wrote:
>
> On 11/19/2016 01:25 PM, Gregg Reynolds wrote:
>>
>> thanks, I was able to build with the latest master.
>>
>> fwiw IMHO the 1.2.0 tarball should be pulled. it looks very bad to make
>> an official release that doesn't even build!
>
>
> I agre
; git
checkout v0.3.2? to use the previous version of TinyCBOR.
>
>
>
> From: iotivity-dev-bounces at lists.iotivity.org [mailto:
iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Gregg Reynolds
> Sent: Saturday, November 19, 2016 11:52 AM
> To: iotivity-dev
> Subject: [
> [mailto:iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Gregg
> Reynolds
> *Sent:* Saturday, November 19, 2016 11:52 AM
> *To:* iotivity-dev
> *Subject:* [dev] 1.2.0 build failure
>
>
>
> $ scons
>
>
>
> ...
>
>
>
> resource/csdk/se
ivity-dev-bounces at lists.iotivity.org
> <mailto:iotivity-dev-bounces at lists.iotivity.org>
> [mailto:iotivity-dev-bounces at lists.iotivity.org
> <mailto:iotivity-dev-bounces at lists.iotivity.org>] On Behalf Of Gregg
> Reynolds
>> Sent: Saturday, November 1
$ scons
...
resource/csdk/security/src/aclresource.c: In function 'AclToCBORPayload':
resource/csdk/security/src/aclresource.c:628:24: error: 'CborEncoder' has
no member named 'ptr'
*size = encoder.ptr - outPayload;
^
resource/csdk/security/src/aclresource.c:640:2
29 matches
Mail list logo
