Vojta, is this something that you can check / change on the machine which actually builds ci nightly?
Thanks, Jakub On 4/14/19 6:35 PM, Matthieu Riolo wrote: > Hello everyone > > Last week I looked into the issue to why the CI build for python2 does not > build. Looking at the logs and comparing it with the result of my machine I > come to the conclusion that the CI machine is not set up correctly. > > Here the relevant informations I gathered: > The python2 build uses two stages. In the first stage it compiles > python-native. This program will run on CI and helps to build the second > stage. In the second stage it builds python-cross, which is actually the > binary which will run in HelenOS. > > As it turns out, python-native compiles fine. But once the build scripts > tries to use python-native to compile python-cross, it fails. This can be > seen from the following CI log > > http://ci.helenos.org/latest/logs/coastline-build-python2-for-amd64.log > ./python -E -S -m sysconfig --generate-posix-vars > Could not find platform dependent libraries <exec_prefix> > > Python-native seems to fail, because it’s not able to find the module > „sysconfig“. My guess is, that it fails because the environment variable > PYTHONHOME is set to a faulty location. On my machine the variable is not set > and python-native will automatically use the execution directory as search > path for the modules. The path used by python-native should look like this: > /helenos-harbour/build/python2/python-native/Lib > > > Best Regards > Matthieu Riolo > > > PS: I run centos 7 on a x86 machine > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
