Re: [blfs-dev] libinput
Wayne Blaszczyk wrote:
On Sat, 2016-07-23 at 17:05 -0500, Bruce Dubbs wrote:
I am in the process of updating libinput and have a couple of issues I'd
like to discuss.
First, several months ago I moved libinput into xorg drivers. Upon
review, that may have been a mistake. There is nothing in Xorg that uses
it. The references in the book are:
general/sysutils/weston.xml: ,
gnome/platform/mutter.xml:,
kde/plasma5/plasma-all.xml: ,
x/lib/qt5.xml:
x/lib/clutter.xml:,
xfce/core/xfce4-settings.xml:
IIRC, I moved libinput from General Libraries where Armin placed it
initially. I now propose moving it back.
Second, the build and install of libinput-1.4.0 is straight forward, but
virtually all the checks fail. In order to run the checks both the check
program and valgrind need to be installed. However most of the checks are
based on valgrind and valgrind fails. This is because we strip
/lib/ld-2.23.so with --strip unneeded in LFS.
When checking some major distros, they make a ld-2.23.so.dbg file
available as a replacement for the normally stripped ld-2.23.so file that
would be installed with something like:
ld-linux-x86-64.so.2 -> ld-2.23.so.dbg
This file comes from glibc.
The question here is how to handle it. We can change the LFS stripping
procedure to do something like:
cp /lib/ld-2.23.so /tmp/ld-2.23.so.dbg
and then continue with
/tools/bin/find /lib /usr/lib -type f -name \*.so* \
-exec /tools/bin/strip --strip-unneeded {} ';'
mv /tmp/ld-2.23.so.dbg /lib
Then users can use the .dbg version just by changing the
ld-linux-x86-64.so.2 symlink.
Another option is to say that libinput does not come with a workable test
suite.
A third option is to describe the issue and say how to test the package
but that we have not run the tests.
I'm leaning toward this third option, but only slightly.
I appreciate any thoughts you may have about this package.
I was going to bring this up several months ago when I was looking into
going 100% wayland, but it slipped by the wayside. I agree that it does
not belong in the XORG section and should be moved out. But I did come
across the following xorg driver, xf86-input-libinput (X.Org libinput driver)
which I have started using.
There is a blurb about it at the bottom of this page:
https://www.freedesktop.org/wiki/Software/libinput/
BTW, I gave up on wayland (gnome) as there are still many unresolved issues,
namely no mouse locking (for FPS games) among other things.
Thanks Wayne. We probably should investigate that for the next cycle, but
we've made a lot of changes in the last few months with sysv/systemd
integration for the books, restoring gnome, and going to kde5 only.
-- 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] libinput
On Sat, 2016-07-23 at 17:05 -0500, Bruce Dubbs wrote:
> I am in the process of updating libinput and have a couple of issues I'd
> like to discuss.
>
> First, several months ago I moved libinput into xorg drivers. Upon
> review, that may have been a mistake. There is nothing in Xorg that uses
> it. The references in the book are:
>
> general/sysutils/weston.xml: ,
> gnome/platform/mutter.xml:,
> kde/plasma5/plasma-all.xml: ,
> x/lib/qt5.xml:
> x/lib/clutter.xml:,
> xfce/core/xfce4-settings.xml:
>
> IIRC, I moved libinput from General Libraries where Armin placed it
> initially. I now propose moving it back.
>
> Second, the build and install of libinput-1.4.0 is straight forward, but
> virtually all the checks fail. In order to run the checks both the check
> program and valgrind need to be installed. However most of the checks are
> based on valgrind and valgrind fails. This is because we strip
> /lib/ld-2.23.so with --strip unneeded in LFS.
>
> When checking some major distros, they make a ld-2.23.so.dbg file
> available as a replacement for the normally stripped ld-2.23.so file that
> would be installed with something like:
>
> ld-linux-x86-64.so.2 -> ld-2.23.so.dbg
>
> This file comes from glibc.
>
> The question here is how to handle it. We can change the LFS stripping
> procedure to do something like:
>
> cp /lib/ld-2.23.so /tmp/ld-2.23.so.dbg
>
> and then continue with
>
> /tools/bin/find /lib /usr/lib -type f -name \*.so* \
> -exec /tools/bin/strip --strip-unneeded {} ';'
>
> mv /tmp/ld-2.23.so.dbg /lib
>
> Then users can use the .dbg version just by changing the
> ld-linux-x86-64.so.2 symlink.
>
> Another option is to say that libinput does not come with a workable test
> suite.
>
> A third option is to describe the issue and say how to test the package
> but that we have not run the tests.
>
> I'm leaning toward this third option, but only slightly.
>
> I appreciate any thoughts you may have about this package.
>
> -- Bruce
I was going to bring this up several months ago when I was looking into
going 100% wayland, but it slipped by the wayside. I agree that it does
not belong in the XORG section and should be moved out. But I did come
across the following xorg driver, xf86-input-libinput (X.Org libinput driver)
which I have started using.
There is a blurb about it at the bottom of this page:
https://www.freedesktop.org/wiki/Software/libinput/
BTW, I gave up on wayland (gnome) as there are still many unresolved issues,
namely no mouse locking (for FPS games) among other things.
Regards,
Wayne.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] libinput
I am in the process of updating libinput and have a couple of issues I'd
like to discuss.
First, several months ago I moved libinput into xorg drivers. Upon
review, that may have been a mistake. There is nothing in Xorg that uses
it. The references in the book are:
general/sysutils/weston.xml: ,
gnome/platform/mutter.xml:,
kde/plasma5/plasma-all.xml: ,
x/lib/qt5.xml:
x/lib/clutter.xml:,
xfce/core/xfce4-settings.xml:
IIRC, I moved libinput from General Libraries where Armin placed it
initially. I now propose moving it back.
Second, the build and install of libinput-1.4.0 is straight forward, but
virtually all the checks fail. In order to run the checks both the check
program and valgrind need to be installed. However most of the checks are
based on valgrind and valgrind fails. This is because we strip
/lib/ld-2.23.so with --strip unneeded in LFS.
When checking some major distros, they make a ld-2.23.so.dbg file
available as a replacement for the normally stripped ld-2.23.so file that
would be installed with something like:
ld-linux-x86-64.so.2 -> ld-2.23.so.dbg
This file comes from glibc.
The question here is how to handle it. We can change the LFS stripping
procedure to do something like:
cp /lib/ld-2.23.so /tmp/ld-2.23.so.dbg
and then continue with
/tools/bin/find /lib /usr/lib -type f -name \*.so* \
-exec /tools/bin/strip --strip-unneeded {} ';'
mv /tmp/ld-2.23.so.dbg /lib
Then users can use the .dbg version just by changing the
ld-linux-x86-64.so.2 symlink.
Another option is to say that libinput does not come with a workable test
suite.
A third option is to describe the issue and say how to test the package
but that we have not run the tests.
I'm leaning toward this third option, but only slightly.
I appreciate any thoughts you may have about this package.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
