On Sun, 19 Jan 2020 at 14:18, DJ Lucas via lfs-dev
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
On Sun, 19 Jan 2020 at 14:18, DJ Lucas via lfs-dev
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
On 1/19/2020 12:17 AM, DJ Lucas via lfs-dev wrote:
See https://legacy.python.org/dev/peps/pep-3149/for rationale
Sorry, bad link. https://legacy.python.org/dev/peps/pep-3149/
--DJ
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe:
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.
ac_python_version=`$PYTHON -c 'import
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.
I am asking similar questions, albeit with more of a Xen focus,
on the Xen developers list.
The first
