Based on those logs, I think the specific problem has already been fixed. Can you try the current "top" of RB-1.6 to verify? If it works, I'll tag the current top and declare a new release if you need.
We just recently started having the Travis-CI tests include a debug build (and that's why it is already fixed), so hopefully this kind of problem will be more rare in the future. So, how can we cut down even more to reduce the chances of breaking your builds (and then us having to track it down and cut new releases just to fix it)? There are a few things to consider: * Almost always, the Debian build breaks are "warnings" that are treated as errors. You may wish to consider compiling with STOP_ON_WARNING=0 as standard practice, and only every once in a while compile without it and report back to us any errors you encounter -- OR, compile the usual way by default but know that if it fails, try again with STOP_ON_WARNING=0 and use that build if it succeeds. In any case, if STOP_ON_WARNING=0 succeeds, you should go with that build. If you send us the logs, we can address the warning as promptly as we can, but it should never hold up your updating the package. The warnings are almost always harmless. * This particular problem (and some others we've had for your builds, IIRC) are in a DASSERT, and thus only a build break for DEBUG builds. I think you should seriously consider the merits of building in DEBUG mode. Why is it helpful to your users? It seems to me that anyone who needs to debug *into* OIIO can probably build from source, and for everybody else it's probably a distraction and they would prefer only an optimized build? Is there a good reason to provide a debug build? Is that standard for all libraries? * Is there a way you can do a nightly (or less frequently, but periodic) builds that can catch these little breakages as soon as they go in, rather than only after we've tagged a release? > On Jan 8, 2016, at 12:22 AM, Matteo F. Vescovi <[email protected]> wrote: > > Hi! > > On Fri, Jan 8, 2016 at 8:55 AM, Ghislain Vaillant <[email protected]> wrote: >> Works if you disable error on warnings with -DSTOP_ON_WARNING=OFF. I believe >> I mentioned this fix in the private email exchange we had yesterday. > > Well, it sounds to me like a workaround more than a fix and I didn't > mention in my reply to your private mail because I was preferring > finding a better solution, that is asking the upstream > developer/maintainer in this case ;-) > > Let's wait and hear something from Larry. > > Cheers. > > -- > Matteo F. Vescovi -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
