Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: libunwind files in /usr/libexec ? (Read 304 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

libunwind files in /usr/libexec ?

Hello,

According to the Arch package guidelines,
it specifically says: "Avoid using /usr/libexec/ for anything. Use /usr/lib/$pkgname/ instead."

Looking at the latest release of libunwind,
it says: "By default these executables are installed in ${libexecdir}/libunwind where ${libexecdir} defaults to ${prefix}/libexec, but all this can be set explicitly though arguments to configure."

However, I have these files on my system:

Code: [Select]
$ pacman -Ql libunwind
[...]
libunwind /usr/libexec/
libunwind /usr/libexec/libunwind/
libunwind /usr/libexec/libunwind/Gperf-simple
libunwind /usr/libexec/libunwind/Gperf-trace
libunwind /usr/libexec/libunwind/Gtest-bt
libunwind /usr/libexec/libunwind/Gtest-concurrent
libunwind /usr/libexec/libunwind/Gtest-exc
libunwind /usr/libexec/libunwind/Gtest-init
libunwind /usr/libexec/libunwind/Gtest-resume-sig
libunwind /usr/libexec/libunwind/Gtest-resume-sig-rt
libunwind /usr/libexec/libunwind/Gtest-trace
libunwind /usr/libexec/libunwind/Gx64-test-dwarf-expressions
libunwind /usr/libexec/libunwind/Lperf-simple
libunwind /usr/libexec/libunwind/Lperf-trace
libunwind /usr/libexec/libunwind/Lrs-race
libunwind /usr/libexec/libunwind/Ltest-bt
libunwind /usr/libexec/libunwind/Ltest-concurrent
libunwind /usr/libexec/libunwind/Ltest-exc
libunwind /usr/libexec/libunwind/Ltest-init
libunwind /usr/libexec/libunwind/Ltest-init-local-signal
libunwind /usr/libexec/libunwind/Ltest-mem-validate
libunwind /usr/libexec/libunwind/Ltest-nocalloc
libunwind /usr/libexec/libunwind/Ltest-nomalloc
libunwind /usr/libexec/libunwind/Ltest-resume-sig
libunwind /usr/libexec/libunwind/Ltest-resume-sig-rt
libunwind /usr/libexec/libunwind/Ltest-trace
libunwind /usr/libexec/libunwind/Ltest-varargs
libunwind /usr/libexec/libunwind/Lx64-test-dwarf-expressions
libunwind /usr/libexec/libunwind/check-namespace.sh
libunwind /usr/libexec/libunwind/crasher
libunwind /usr/libexec/libunwind/forker
libunwind /usr/libexec/libunwind/mapper
libunwind /usr/libexec/libunwind/run-coredump-unwind
libunwind /usr/libexec/libunwind/run-coredump-unwind-mdi
libunwind /usr/libexec/libunwind/run-ptrace-mapper
libunwind /usr/libexec/libunwind/run-ptrace-misc
libunwind /usr/libexec/libunwind/test-async-sig
libunwind /usr/libexec/libunwind/test-coredump-unwind
libunwind /usr/libexec/libunwind/test-flush-cache
libunwind /usr/libexec/libunwind/test-init-remote
libunwind /usr/libexec/libunwind/test-mem
libunwind /usr/libexec/libunwind/test-proc-info
libunwind /usr/libexec/libunwind/test-ptrace
libunwind /usr/libexec/libunwind/test-ptrace-misc
libunwind /usr/libexec/libunwind/test-reg-state
libunwind /usr/libexec/libunwind/test-runner
libunwind /usr/libexec/libunwind/test-setjmp
libunwind /usr/libexec/libunwind/test-static-link
libunwind /usr/libexec/libunwind/test-strerror
libunwind /usr/libexec/libunwind/x64-unwind-badjmp-signal-frame

Shouldn't they go to /usr/lib instead?

Re: libunwind files in /usr/libexec ?

Reply #1 –
Maybe they, or at least some of them, don't need to be installed at all ?
To quote more of the context of the text and link you posted.
Quote
One of the functional changes is that the testsuite is now installed with a make install, which may affect downstream packagers. By default these executables are installed in ${libexecdir}/libunwind where ${libexecdir} defaults to ${prefix}/libexec, but all this can be set explicitly though arguments to configure.

So the test suite now gets installed.

The upstream Arch package is the same.

Re: libunwind files in /usr/libexec ?

Reply #3 –
Fixed by commit