On 8/8/2018 1:01 PM, bju...@ymail.com wrote: > Blosc is currently blocking a full build using recent versions of gcc on > Linux. Upgrading by two revisions (to 1.8.1 I believe ) addresses the issue > directly. It's currently tagged for an update to 1.14.3
> This issue may have been what kicked off the library update review? It's really not, the review had been on the schedule for quite a while now, but an ancient compiler on windows was blocking some of the updates. > It would be a pity if it was the last to be updated. It will be don't worry. --Ray > I am away from my build machine so please forgive me if the change has > already been made. > > Justin Jones > > On August 8, 2018 9:54:58 AM MDT, Brecht Van Lommel > <brechtvanlom...@gmail.com> wrote: >> Hi all, >> >> Regarding how to get this moving further, I had a quick talk with >> Sergey. >> To avoid the Linux part being a bottleneck, I suggest to update the >> Windows >> and macOS libraries as soon as they are ready, and commit the build >> environment CMake changes alongside them. It's not a big deal if the >> platform versions are out of sync for a bit, and Sergey can do the >> corresponding updates for Linux when he has time. >> >> So Ray and Arto can just coordinate committing these changes amongst >> themselves. If any C/C++ code needs to change we can use #ifdef's, >> which we >> want anyway in case Linux users are compiling against different library >> versions. >> >> Thanks, >> Brecht. >> >> On Sat, Aug 4, 2018 at 9:01 PM Bastien Montagne <montagn...@wanadoo.fr> >> wrote: >> >>> Don’t think we are in urgent hurry here, we can give it a few more >> weeks >>> and see whether 3.7.1 emerges in time for us (would say dead line for >>> libs update would be end of September?) >>> >>> >>> On 03/08/2018 10:57, Sergey Sharybin wrote: >>>> One thing which is raising my attention in 3.7.1 release log is: >>>> >>>> - Fixed a performance regression for reading streams with tarfile. >>>> >>>> Also, 3.7.1 is planned to be released soon-ish? Their original plan >>>> actually mentions July, not sure what is the updated planning. Are >> we >>>> really in a hurry for this update? >>>> >>>> On Fri, Aug 3, 2018 at 10:46 AM Sybren A. Stüvel <syb...@stuvel.eu> >>> wrote: >>>>> On 23/07/2018 19:43, Brecht Van Lommel wrote: >>>>>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so >> with >>>>>> bugfixes?) >>>>> Let's go to 3.7.0, unless somebody already knows of actual bugs >> that'll >>>>> influence our use. >>>>> >>>>> Sybren >>>>> >>>>> _______________________________________________ >>>>> Bf-committers mailing list >>>>> Bf-committers@blender.org >>>>> https://lists.blender.org/mailman/listinfo/bf-committers >>>>> >>> _______________________________________________ >>> Bf-committers mailing list >>> Bf-committers@blender.org >>> https://lists.blender.org/mailman/listinfo/bf-committers >>> >> _______________________________________________ >> Bf-committers mailing list >> Bf-committers@blender.org >> https://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > https://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org https://lists.blender.org/mailman/listinfo/bf-committers