e176b8ec19
readelf --debug-dump sometimes reports inscrutable warnings which don't actually affect our extraction of source filenames. For example: readelf: Warning: There is a hole [0xd3d - 0xd89] in .debug_loc section. Now gcc 11 seems to have dramatically increased the number of warnings: readelf: Warning: Corrupt offset (0x0000008e) in range entry 9 [...] readelf: Warning: Corrupt offset (0x000010f0) in range entry 250 The resulting debuginfo created by the very same toolchain works fine, as does the list of source filenames. But the warnings are quite noisy... send them to /dev/null since they are not actionable in the context of getting source files Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org> |
||
|---|---|---|
| .. | ||
| docs.sh.in | ||
| emptydirs.sh.in | ||
| libtool.sh.in | ||
| meson.build | ||
| purge.sh.in | ||
| staticlibs.sh.in | ||
| strip.sh.in | ||
| zipman.sh.in | ||