Skip to content
GitLab
Open
Issue created by Felix Moessbauer@fmoessbauerContributor3 of 8 checklist items completed3/8 checklist items

Simplify packaging of DynamoRIO

Add a pointer to any prior users list discussion.

This issue is a follow up of the discussion started in #5152.

Is your feature request related to a problem? Please describe.

Currently, packaging of DynamoRIO for OS distributions like Debian is not possible (without patches) due to a list of incompatibilities. The following list should help to keep track of the current status and changes that will be required.

Describe the solution you'd like

The following aspects should be changed:

  • CMake
    • Add support for install-relocation via DESTDIR env variable #5152
    • libdynamorio-dev: Make CMake scripts of DynamoRIO work with system install paths
    • libdynamorio-dev: Make export targets relocatable (make LIBDIR / BINDIR configurable via cache variable)
  • drrun
    • rework injection logic to support other directory structures as well (e.g. /usr/lib/<multiarch-triplet>/dynamorio.so, config in /etc/dynamorio, etc...)
      • #5548
      • #5443
    • Find installed dynamorio tools / clients via conf.d style integration (each new client drops a file in /etc/dynamorio/tools.d/). This makes it possible for third-party tools that are packaged as well to easily integrate into DR.
  • Libraries
    • Check if the libdynamorio.so needs the execution bit or if there are other strategies. Installing a library with execution bit set is discouraged or even forbidden for some distros. (It is required!)
    • Add SO version, describing ABI compatibility
    • Do not rely on checked-in binaries (like elftc). These should always be built from the sources (e.g. via externalProject). Xref #4422

Describe alternatives you've considered

It is possible to work around some limitations (like expected directory layout of drrun) by using wrappers and ignoring checks. However, this is neither a clean solution, nor sustainable.

Additional context