On 12/16/2018 04:21 PM, Pierre Labastie via blfs-dev wrote:
On 16/12/2018 18:57, Pierre Labastie via blfs-dev wrote:
On 16/12/2018 18:05, Bruce Dubbs via blfs-dev wrote:
On 12/16/2018 10:33 AM, Pierre Labastie via blfs-dev wrote:
On 16/12/2018 16:52, Pierre Labastie via blfs-dev wrote:
On 13/12/2018 23:05, Bruce Dubbs via blfs-dev wrote:
I just updated to mesa-18.3.1 earlier today. A couple of things I found
after
reading this thread:
1. Package libtizcore was not found. We don't have this mentioned and I
don't know what it does. I did find
https://github.com/tizonia/tizonia-openmax-il/tree/master/libtizcore but
there
is no documentation.
There is only one file in src/. It is a 1900 line .c file. A comment:
* This library implements the base OpenMAX IL Core infrastructure, as
* specified in the standard.
But I don't know what that means. Google points to
https://www.khronos.org/openmaxil but a very fast scan indicates to me
that we
don't need it.
2. Using PYTHON=python3 in the configure works. If P2 is not present, then
I suspect that it would pick it up automatically, but I've not tried.
2a. The make log only references python3 once.
3. It does look for mako.
4. We could switch to meson.
A couple of remarks about mesa+P3:
- I think I will not be able to test building mesa with only P3 available. The
reason is that I need llvmpipe, and that LLVM seems to require P2 (although
some work seems to have been done in order to support P3 (see e.g. [1] and
[2]) for some time now.
Update: according to the documentation [1], Python seems to be only required
for tests. As anybody tested that Python is not needed if the tests are not
run (and/or built, that is P2 could be needed as soon as -DLLVM_BUILD_TESTS is
ON)? If this is the case, we could make P2 optional for llvm, remove the
"-DLLVM_BUILD_TESTS=ON" flag, and expand the test section to mention this flag.
- [...]
Pierre
[1] https://llvm.org/docs/GettingStarted.html#software
I am getting ready to do a new build on my laptop. Normally I don't need llvm
for mesa on that system, but I can do the build and test without P2.
I plan to start later today or tomorrow.
Thanks,
Actually, I am just starting an LLVM build right now in a VM; without Python2
installed (only Python3 from LFS). Cmake found python3 and seems OK with that.
Will let you know if it completes. I've removed the -DLLVM_BUILD_TESTS=ON switch
It completed, and actually, also building mesa, and X.
The full "X Window System environment" has been built without Python2 on the
machine. And it started with "startx" as usual.
I'm still building xorg as a part of a full rebuild on my laptop. I do
not have P2 installed. I did build P3 mako as a dependency for mesa and
I got:
Processing dependencies for Mako==1.0.7
Searching for MarkupSafe>=0.9.2
Reading https://pypi.python.org/simple/MarkupSafe/
Downloading
https://files.pythonhosted.org/packages/e4/c4/adcc2d6f2ac2146cc04e076f14f1006c1de8e1e747fa067668b6573000b8/MarkupSafe-1.1.0-cp37-cp37m-manylinux1_x86_64.whl#sha256=d9ac82be533394d341b41d78aca7ed0e0f4ba5a2231602e2f05aa87f25c51672
Best match: MarkupSafe 1.1.0
Processing MarkupSafe-1.1.0-cp37-cp37m-manylinux1_x86_64.whl
Installing MarkupSafe-1.1.0-cp37-cp37m-manylinux1_x86_64.whl to
/usr/lib/python3.7/site-packages
Adding MarkupSafe 1.1.0 to easy-install.pth file
So it works like cpan and downloads/builds/installs dependencies if they
are not present. I note that Beaker is not mentioned though.
mesa configure gives:
hecking for a Python interpreter with version >= 2.7... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.7
checking for python3 platform... linux
checking for python3 script directory...
${prefix}/lib/python3.7/site-packages
checking for python3 extension module directory...
${exec_prefix}/lib/python3.7/site-packages
...
checking if module mako in python is installed... yes
In my make log, there is no mention of python at all.
In the check log, there is no mention of python at all.
The bottom line is that I think we can make P2 optional for mesa and say
that it's not needed since P3 is installed in LFS.
For mako I think we can drop the Beaker dependency (indeed all of Beaker
and funcsigs) and only build the P3 version of mako. (Agreeing with Pierre)
We may need to keep the P2 version of MarkupSafe since it is used by
jinja2 in the systemd version of kf5. I don't know if that is P2 or P3
or both. Looking at the source for kapidox, I see
build/lib/kapidox/generator.py:
# Python 2/3 compatibility (NB: we require at least 2.7)
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
