diff options
| author | orbea <orbea@riseup.net> | 2021-04-01 19:01:54 -0700 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2021-04-04 09:27:35 +0200 |
| commit | 68913466af49c738d7e226f55db15be70b22dbe6 (patch) | |
| tree | 62d6655bc2ce08c4f7cb2ccab3275acc6aa72697 /src/core/systemd/src/libsystemd-network/lldp-neighbor.c | |
| parent | 74fc2793417a5e5b1bc366b3fb42bb3aa2fe3cf7 (diff) | |
| download | NetworkManager-68913466af49c738d7e226f55db15be70b22dbe6.tar.gz | |
tools: use libtool --mode=execute
Better fix for https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/732
The original issue was that when compiling NetworkManager with slibtool
the create-exports-NetworkManager.sh script gave the NetworkManager-all-sym
slibtool wrapper script to nm(1) instead of the actual binary. This is
because slibtool and GNU libtool do not place the compiled programs in
the same location. The original fix was to test both locations, but this
is bit of a hack especially since the build system should not be using the
.libs directory directly. However with $(LIBTOOL) --mode=execute this is
not a problem since both implementations can figure out where the correct
binary is.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/805
Diffstat (limited to 'src/core/systemd/src/libsystemd-network/lldp-neighbor.c')
0 files changed, 0 insertions, 0 deletions