El 8/12/24 a las 20:59, Thomas Lange escribió:
As far as I understand the policy, parallel builds are not mandatory. I also did not defined parallel=n in the rules file or in DEB_BUILD_OPTIONS.
It's funny that some people who want to avoid fixing Makefile bugs which happens 100% of the time when there is only one CPU say exactly the opposite, that sequential builds are not mandatory... Obviously one of the claims may not be true. Do you have an opinion about what Matthias Klose said in the last message of this bug? I'm curious about what you think: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081448 What Policy really says is that when build-dependencies are installed the build must succeed, and it does not say anything about the number of CPUs, so yes, this is a FTBFS bug, because the build must always work. Of course, if there is a bug in the Makefiles and you choose to disable parallelism to avoid the build to fail, that's a completely acceptable way to fix the FTBFS bug. So, in some sense, you are right, but only when we use the right wording to express it: Nobody will tell you that your package should build in parallel when there is more than one CPU. We just want the build to work in all systems.
I've added .NOTPARALLEL: pdf text to doc/Makefile so the two a2x command will not be run in parallel any more.
Fine. I wonder if you managed to reproduce the problem. Did that really fix the problem or you just think it would? Thanks.
