Hello Nitheesh and all,

I am looking at the patch content. As far as I can understand, it adds
"0.0.1" to all the shared libraries version, and moved the libraries into a
separate folder 'libs'.
In the mailing list message, you mention:

I was able to fix the issue by modifying the build scripts to
forcefully add a SONAME to the generated shared libs during build.

*(-wl, -soname,<lib>)*


Is it the whole fix?

Regards,
Max



On Mon, Jan 23, 2017 at 12:40 AM, K L, Nitheesh <nitheesh.k.l at intel.com>
wrote:

> Hi Salvatore,
>
> https://gerrit.iotivity.org/gerrit/#/c/4867/ - was my fix last year.
> I don?t think this got merged, but I think another version of similar
> patch was integrated.
> Haven't followed it since then.
> Anyway, may be this patch might help you point in the right direction.
>
> Cheers!
> Nitheesh
>
> -----Original Message-----
> From: Iovene, Salvatore [mailto:salvatore.iovene at intel.com]
> Sent: Thursday, January 19, 2017 4:18 AM
> To: iotivity <iotivity-dev at lists.iotivity.org>
> Cc: K L, Nitheesh <nitheesh.k.l at intel.com>; Rahul, Rahul <
> rahul.rahul at intel.com>
> Subject: Post reprise: "android example apps crash with SDKVersion 23"
>
> Hi,
> this email is in reference of the following thread from exactly one year
> ago:
>
> https://lists.iotivity.org/pipermail/iotivity-dev/2016-January/003396.html
>
> Has a fix been planned for this?
>
> Nitheesh, have you been able to apply a workaround or a custom patch to
> fix it in your builds?
> Rahul, would be be able to look into it?
>
> Thanks in advance!
> Salvatore
>
> --
> Salvatore Iovene <salvatore.iovene at intel.com> Linux Software Engineer
> Intel Open Source Technology Center, Finland
> Tel.: +358504804026
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170123/4eaafdb0/attachment.html>

Reply via email to