I'm trying to get the BLFS tests for libinput to run. Among the instructions is a commented hunk about valgrind needing debugging symbols:
<para> To run the tests for this package, valgrind requires a version of the /lib/ld-2.23.so (or later) library with debugging symbols present. Normally in LFS these debugging symbols are stripped at the end of Chapter 6. To get this library, glibc must be rebuilt with the current glibc version using the same compiler that was used to build LFS. The ld-2.23.so can then be renamed to ld-2.23.so.dbg and copied to /lib. Then a symlink needs to be changed:</para> <screen role="nodump"><userinput>ln -sfv ld-2.23.so.dbg /lib/ld-linux-x86-64.so.2</userinput></screen> Followed by a commented note that the testsuite can cause problems (dummy input devices leading to crashing a local X server or a desktop environment). Spooky, but apparently addressed by the instructions at https://wayland.freedesktop.org/libinput/doc/1.9.1/test-suite.html BUT running ln -svf ld-2.27.so.dbg /lib/ld-linux-x86-64.so.2 makes the system unusable (everything segfaults), the used tty generates the old "respawning too fast" message (at least in sysvinit). Rebooting (Magic_SysRQ, otherwise a power interruption would be required) fails to boot, init killed, kernel panic. So, don't even think of trying this unless you have another system you can use to mount the broken one and revert the symlink change. Is this just me (system is 20180615), or is it definitely broken ? ĸen -- Keyboard not found, Press F1 to continue -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
