Hello Sunil, Sunil Mohan Adapa [2020-01-04 12:15 -0800]: > > This file doesn't exist anywhere -- apparently src/include/builddefs.install > > builds it, but at this point this is pretty deeply woven into the build > > system. > > Curiously, resuming the build with "make" and "dpkg-buildpackage -us -uc > > -b -nc" > > gets over that, but then in the end it still fails with > > I believe the rm commands run during cleanup. I suspect the source is > not conducive to running multiple build/cleanup cycles.
It's the other way around -- I always started from a clean tree. I wanted to debug that further, which is why I ran `make` and a `-nc` build, and noticed that it then made further progress. > I ran into similar issue when attempting to build with multiple parallel > tasks with DEB_BUILD_OPTIONS=parallel=8 or with -j8. If you have this > turned on, please try disabling it. I indeed had that option set, thanks for pointing out! pcp's packaging is rather complex and debian/rules rather old-fashioned and hard to understand, and apparently doesn't get along well with parallel builds. This RC bug fix is not the time for more intrusive changes though, so let's ignore this for now indeed. However, even with unsetting it it still fails: > mv: cannot stat 'Makefile.fix': No such file or directory > make[4]: Makefile: No such file or directory > make[4]: *** No rule to make target 'Makefile'. Stop. > dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned > exit status 2 I can't get around this failure in my sid chroot. And I don't want to embarrass myself by doing a source-only NMU with hoping that it works on the buildds.. Thanks, Martin
