toolbox/playbooks
Debarshi Ray 8dd7ee47c5 build: Drop the use of patchelf(1)
Some downstream distributors like RHEL don't have patchelf(1). Relying
on patchelf(1) during the build will make it difficult for such
downstreams to distribute Toolbox.

Fortunately, the path of the dynamic linker (ie., PT_INTERP) is
hardcoded in the ABI specification of each architecture [1]. This means
that Toolbox's build system can keep it's own architecture to dynamic
linker mapping, and specify it during the build through the GNU ld
linker's --dynamic-linker flag, as opposed to using a tool like
patchelf(1) to change the path of the dynamic linker in the built
binary to the one inside /run/host. Currently, the list of
architectures covers the ones that Fedora builds for.

[1] https://sourceware.org/glibc/wiki/ABIList

https://github.com/containers/toolbox/pull/942
2021-12-09 13:16:27 +01:00
..
setup-env.yaml build: Drop the use of patchelf(1) 2021-12-09 13:16:27 +01:00
system-test.yaml playbooks: Unify test setup for system & unit tests 2021-10-22 16:43:38 +03:00
unit-test.yaml playbooks: Unify test setup for system & unit tests 2021-10-22 16:43:38 +03:00