Bug 1005
Summary: | Build failure with gcc11 in When Using Environment Modules | ||
---|---|---|---|
Product: | DPDK | Reporter: | David Christensen (drc) |
Component: | meson | Assignee: | dev |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | bruce.richardson |
Priority: | Normal | ||
Version: | 22.03 | ||
Target Milestone: | --- | ||
Hardware: | POWER | ||
OS: | Linux |
Description
David Christensen
2022-05-05 18:59:48 CEST
I can resolve the build problem with the following steps: $ meson build $ cd build $ sed --in-place=.BAK1 's|-Wl,-rpath,/lib/../lib64||' build.ninja $ sed --in-place=.BAK2 's|-Wl,-rpath-link,/lib/../lib64||' build.ninja $ cd .. $ ninja -C build ninja: Entering directory `build' [3341/3341] Linking target app/test/dpdk-test $ It's not clear to me where the rpath/rpath-link arguments are being added. The rpath entries are automatically added by meson to the build so that the binaries generated can be run directly from the build directory. When "ninja install" is run, these extra rpaths are removed. From https://mesonbuild.com/Release-notes-for-0-55-0.html "On Linux-like systems, Meson adds rpath entries to allow running apps in the build tree, and then removes those build-time-only rpath entries when installing." |