On Sun, 19 Jan 2020 at 14:18, DJ Lucas via lfs-dev <[email protected]> wrote: > > > On 1/18/2020 9:21 PM, Kevin Buckley via lfs-dev wrote: > > On the back of trying to build Xen 4.12.2 on an LFS system, I've hit > > an issue whereby the Xen M4 python_devel module fails but, even when I > > fix that, Python3 seems to report the "wrong" info. > <snip> > > ac_python_version=`$PYTHON -c 'import distutils.sysconfig; \ > > print(distutils.sysconfig.get_config_var("VERSION"))'` > > This is Python2 syntax. The short answer is to use Python2. > > The longer answer is that you probably have a ton of work to do. > > Also, while it doesn't matter in this case, distutils is (very) slowly > on the way out. If not already dependent on distutils, using python > itself is probably better in the long run for testing the installed > python version, something like: >...
Actually, I am just building Xen from source, it's the Xen developers who are doing the work to make their install work on systems that don't have Python2: Xen itself, omce installed, seems quite happy without Python 2. I habe merely fed back a couple of observations that led to them realising they hadn't covered all the bases. And it's worth pointing out that they are close, not least as I'd built a "non-Release" Xen last year, see: http://youvegotbuckleys.org.nz/LFS/LFS-BOOK.html#ch-xen The issue this year may be that I'd assumed that the 4.12 series, which has seen a couple of releases from commits that are way past the one I used, is therefore now "Python 3 ready", but this,it seems, may not be the case. https://lists.xenproject.org/archives/html/xen-devel/2020-01/msg01478.html Cheers also, by the way, for the "why the pythin libs name have an m", as I had no idea about that. Kevin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
