Hello Steven, Steven Chamberlain a écrit : > The attached patch could have been another way to fix this.
Your patch is smarter than mine, I shall adopt it. > After that, I get to another error: > | -- Check for installed Python Interpreter -- found > | Traceback (most recent call last): > | File "<string>", line 1, in <module> > | ImportError: No module named distutils.sysconfig > | CMake Error at CMakeLists.txt:637 (message): > | Error occurred while attempting to find the Python site library path. /usr/lib/python*/distutils/sysconfig.py files are part of the packages libpython*-stdlib; a build-dependency on libpython-stdlib should not harm. > It could be that some dependency on my system is outdated but I don't > know what exactly. Maybe it won't be a problem on the buildds with > up-to-date sid. > > Complicating this, the error was silently ignored until it fails later > with: Any "silent" error during the run of cmake results in inconsistencies in Makefiles. So it must be taken in account. > > | cd build; export DESTDIR=/«BUILDDIR»/kicad-4.0.2+dfsg1/debian/tmp; make > | install > | make[2]: Entering directory '/«BUILDDIR»/kicad-4.0.2+dfsg1/build' > | make[2]: *** No rule to make target 'install'. Stop. > > The build system also enables -j4 in places without asking, Which test would you ask? Can -j4 be harmful when there are less than 4 cores? I thought that in such a case the number of threads was automatically reduced, isn't it? > and uses > "tee" which causes some buffering of stdout and creates its own buildlog > which isn't really needed. I agree. I had added the "tee" commands to make additional buildlogs when I compiled the package with not yet good enough options. It made it easier to find errors. As now the build system is almost usable, I shall remove those commands. Best regards, Georges.
signature.asc
Description: PGP signature
