| commit | dee2a0e2483bfda415c64f8e168763c63e71f7f6 | |
| author | stk <stk@ableton.com> | |
| Wed, 21 Mar 2018 14:53:12 +0000 (21 15:53 +0100) | ||
| committer | dir <dir@ableton.com> | |
| Mon, 13 Aug 2018 15:54:08 +0000 (13 17:54 +0200) | ||
| tree | 83c060bb6e269ee4267c7e59dac4242faf8bfa69 | treesnapshot (tar.gz zip) |
| parent | 70a42f6597b06f9be12db1bd32bb6a97d4a2e182 | commitdiff |
Remove glib dependency to libelf
It looks like libelf is not used at all by glib, the way it's configured, so
remove it. The problem was that libelf would create a libelf.so.0 file that
was then mistankenly used by perf (instead of the libelf.so.1 file coming from
the elfutils package that it is really supposed to use). This is just the
minimal fix that works for us, because we are not using any other packages that
depend on libelf; to really fix the problem properly, one would have to do
what's mentioned in 2c333655f1 (get rid of libelf by porting existing users
to elfutils).
It looks like libelf is not used at all by glib, the way it's configured, so
remove it. The problem was that libelf would create a libelf.so.0 file that
was then mistankenly used by perf (instead of the libelf.so.1 file coming from
the elfutils package that it is really supposed to use). This is just the
minimal fix that works for us, because we are not using any other packages that
depend on libelf; to really fix the problem properly, one would have to do
what's mentioned in 2c333655f1 (get rid of libelf by porting existing users
to elfutils).