Ugh, looks like the trick I was suggesting doesn't work. It looks like the idiom they're using is inherently at odds with the warning gcc is trying to give.
If your distro includes PugiXML, you could ensure that it is installed and then build OIIO with USE_EXTERNAL_PUGIXML=1 and see if that fixes (dependent on whether Pugi has fixed things upstream). > On Feb 1, 2016, at 11:43 AM, Richard Shaw <[email protected]> wrote: > > I did a copy-n-paste but I may not have got it right... > > /builddir/build/BUILD/oiio-Release-1.6.10/src/include/OpenImageIO/pugixml.cpp: > In member function 'void OpenImageIO::v1_6::pugi::xml_document::create()': > /builddir/build/BUILD/oiio-Release-1.6.10/src/include/OpenImageIO/pugixml.cpp:5143:23: > error: placement new constructing an object of type > 'OpenImageIO::v1_6::pugi::impl::xml_document_struct' and size '88' in a > region of type 'char [1]' and size '1' [-Werror=placement-new] > _root = new ((impl::xml_document_struct *)page->data) > impl::xml_document_struct(page); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > cc1plus: all warnings being treated as errors > > Thanks, > Richard > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
