Re: [blfs-dev] preliminary elogind work
On 12/15/2018 9:00 PM, DJ Lucas via blfs-dev wrote:
> As eudev is to systemd-udev, elogind is to systemd-logind and provides
> org.freedesktop.login1 interface.
All changes mentioned in the previous email message (except for the
xorg-server patch - build changes are there) are in
svn://svn.linuxfromscratch.org/BLFS/branches/{BOOK,bootscripts}-elogind/
Current running merge list is 20827 for BOOK and 20825:20826 for
bootscripts. Next merge for branch begins at 20828 (since I forgot to
add it to the first merge commit message). I'll try to keep them as
large groups of changes to ease merging when/if it comes back into trunk.
Patches have not been uploaded yet and are still in my home directory
for the brave. :-)
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] The wheel group
In 'configuring the /etc/pam.d/ Files' when installing shadow, there is this under 'su': # limit su to users in the wheel group auth requiredpam_wheel.so use_uid I didn't realize blfs had started using the wheel group. I don't see where it is set up in the book. With this line present su gives me a 'permission denied' error and I don't particularly want a wheel group if su is the only reason for one. At present I simply removed this line from /etc/pam.d/su jb. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Python modules dependencies
On 13/12/2018 23:05, Bruce Dubbs via blfs-dev wrote: > On 12/13/2018 03:06 PM, Pierre Labastie via blfs-dev wrote: >> On 13/12/2018 21:44, Brendan L via blfs-dev wrote: >>> On Sun, Dec 9, 2018 at 2:15 AM Pierre Labastie via blfs-dev >>> wrote: On 08/12/2018 23:30, Ken Moffat via blfs-dev wrote: > On Sat, Dec 08, 2018 at 11:11:03PM +0100, Pierre Labastie via blfs-dev > wrote: >> >> Excluding the archive and the .svn directories from the search, it goes >> down >> to 70. Still a lot of work though. Do I understand correctly that we >> could >> remove reference to P2, when it is an optional dependency (even if it >> cannot >> be replaced with P3)? >> >> I've made a small xsl stylesheet to extract python2 dependencies. Here >> is the >> list: package plus dependency type. The stylesheet did not do well with >> python >> modules, but I think it is not that important. > > I think you are looking at an old version of the book, maybe 8.3 ? > >>> Package: Mesa-18.2.6 required >>> >>> Just thought I would chime in to say that Mesa-18.3 is released, which >>> now has python 3 support. I haven't got a chance to test it myself. >>> >> >> Thanks a lot for the information. If mesa supports P3, the whole stack of >> modules for Mako can be made P3 only, I think, and funcsigs can be removed >> (since it is now shipped with core Python since Python 3.3) > > 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. - If Mako is still required (but it seems it wasn't for Bruce), I still plan to move the Mako stack to P3 only, if possible. - (maybe OT respective to the thread, but relevant for mesa) I read in the release notes for mesa that libwayland-egl has been moved to wayland. Do we still need to specify wayland as a platform for mesa? Pierre [1] https://groups.google.com/forum/#!topic/llvm-dev/hPWKyWWerQ4 [2] https://reviews.llvm.org/D42674 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] The wheel group
On 12/16/2018 09:02 AM, John Burrell via blfs-dev wrote: In 'configuring the /etc/pam.d/ Files' when installing shadow, there is this under 'su': |# limit su to users in the wheel group auth required pam_wheel.so use_uid| I didn't realize blfs had started using the wheel group. I don't see where it is set up in the book. With this line present su gives me a 'permission denied' error and I don't particularly want a wheel group if su is the only reason for one. At present I simply removed this line from /etc/pam.d/su wheel was added to /etc/group primarily for systemd. but we added it to sysV for consistency between books. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Python modules dependencies
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 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Python modules dependencies
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. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Python modules dependencies
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 Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] The wheel group
On 12/16/2018 9:02 AM, John Burrell via blfs-dev wrote: > In 'configuring the /etc/pam.d/ Files' when installing shadow, > there is this under 'su': > > |# limit su to users in the wheel group auth required pam_wheel.so > use_uid| > > > I didn't realize blfs had started using the wheel group. I don't see > where it is set up in the book. With this line present su gives me a > 'permission denied' error and I don't particularly want a wheel group > if su is the only reason for one. At present I simply removed this > line from /etc/pam.d/su > > jb. > You can append something like group="sudo" or like. --DJ -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] NetworkManager-1.14.2
On Sat, Dec 15, 2018 at 6:47 PM Roger Koehler via blfs-dev wrote: > > It looks like NetworkManager requires ModemManager now. I can't find a > way to remove the dependency on mm-glib. -Dlibmm-glib=false didn't > work. I used -Dmodem_manager=false and it works for me. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Python modules dependencies
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. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Python modules dependencies
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
