I wouldn't expect 1.6 to work any better than 1.5 (unless I've forgotten to backport something related to gcc5 compatibility, which I could do easily).
I'm betting the issue is boost compiled with gcc 5.x (and perhaps C++11) clashing with OIIO compiled with gcc 4.x/C++03. If boost is a given for gcc5/C++11, there's no reason not to use those for OIIO as well, unless there is another package dependent on OIIO that itself still requires older gcc. > On Aug 10, 2015, at 6:30 AM, Ghislain Vaillant <[email protected]> wrote: > > On 10/08/15 13:38, Matteo F. Vescovi wrote: >> Hope this get fixed soon, or I'll jump directly to OIIO 1.6.xx ;-) > > How about having the current release of 1.6.x packaged in debian/experimental > in the future? > > Ghis -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
