| Summary: | dev-util/meson calls directly nm | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | William Hubbs <williamh> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | floppym |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 243502 | ||
| Attachments: | build.log | ||
|
Description
Agostino Sarubbo
2020-04-16 13:54:02 UTC
Created attachment 633252 [details]
build.log
build log and emerge --info
This is actually Meson doing it, in symbolextractor.py.
It reads the NM environment variable, and falls back to 'nm'. I'm honestly not sure why calling nm directly is a problem. I understand for CC, LD, etc.
> evar = 'NM'
> if evar in os.environ:
> nmbin = os.environ[evar].strip()
> else:
> nmbin = 'nm'
*** Bug 718030 has been marked as a duplicate of this bug. *** *** Bug 718158 has been marked as a duplicate of this bug. *** The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d2d332b15f52b5aadcdc85a6d84d1bcbd99db44f commit d2d332b15f52b5aadcdc85a6d84d1bcbd99db44f Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2020-04-20 15:14:37 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2020-04-22 18:08:28 +0000 meson.eclass: export NM and READELF variables These are used by the symbolextractor.py script in meson. Closes: https://bugs.gentoo.org/717720 Signed-off-by: Mike Gilbert <floppym@gentoo.org> eclass/meson.eclass | 5 +++++ 1 file changed, 5 insertions(+) |