severity 912910 wishlist thanks On Sun, 4 Nov 2018 21:36:14 +0100 Mattia Rizzolo <mat...@debian.org> wrote: > Source: boost1.67 > Version: 1.67.0-9 > Severity: serious > Control: clone -1 -2 boost1.62 1.62.0+dfsg-10 > Control: retitle -2 boost1.62: for loops without set -e > Justification: Policy ยง4.6 > > > Hi boost maintainers, > > I've noticed that your for loops in your rules files are buggy. > This things: > > for pyver in $(pyversions); do \ > echo "Building Boost.Python for python version $$pyver"; \ > $(JAM) --build-dir=build-$$pyver --stagedir=stage-$$pyver > --user-config=$(CURDIR)/user-config-$$pyver.jam --with-python --with-mpi > python=$$pyver; \ > done > > is buggy, as it wouldn't cause a build failure in the instance $(JAM) > failed.
This is intentional, such that when new pythons are added as supported the build doesn't fail, as it is typical that adjustments are needed. I do not believe this is in fact serious. As the build does error out eventually, if none of the pythons managed to build. I am planning to change this a bit, such that the default first build is done with the default python3 enabled. Such that only python2 / other supported python3s may fail to compile. I don't believe this is serious at all. Are you working on testing python3.8 or some such and noticed lack of compat? Regards, Dimitri.
