You could try the make/cmake option USE_EXTERNAL_PUGIXML=1 to try to get it to use the system-installed PugiXML, if there is one. That might help if the system version has been updated to avoid the warning.
Or, build with STOP_ON_WARNING=0 to not let warnings like this hold up the build. Or, try the change I suggested, see if that gets you unstuck. > On Feb 1, 2016, at 12:38 PM, Matteo F. Vescovi <[email protected]> wrote: > > Hi! > > Il 01/feb/2016 20:46, "Richard Shaw" <[email protected] > <mailto:[email protected]>> ha scritto: > > > > Not sure if this helps but I think this is the upstream bug: > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67942 > > <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67942> > Something similar here: > > https://bugs.debian.org/812051 <https://bugs.debian.org/812051> > Larry, do you remember that in our Hangout few days ago you pointed me to add > a Cmake parameter about Pugixml? Probably this is the case. > > Hope this helps somehow. > > Cheers. > > mfv > > _______________________________________________ > 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
