Skip to content

add nm to build#135

Open
m-hemmings wants to merge 2 commits intomainfrom
134-add-llvm-nm-to-buildtoolchainenv
Open

add nm to build#135
m-hemmings wants to merge 2 commits intomainfrom
134-add-llvm-nm-to-buildtoolchainenv

Conversation

@m-hemmings
Copy link
Member

WHAT CHANGED

  • preflight now discovers NM from:
    • $(LIND_WASM_ROOT)/clang+llvm-18.1.8-x86_64-linux-gnu-ubuntu-18.04/bin/llvm-nm
    • command -v llvm-nm
  • preflight now fails if llvm-nm is missing (ERROR: llvm-nm not found ...).
  • build/.toolchain.env now exports NM along with CLANG, AR, RANLIB.
  • print-config now prints NM.

@m-hemmings m-hemmings linked an issue Mar 10, 2026 that may be closed by this pull request
@m-hemmings
Copy link
Member Author

Can't run the cloud build check until merge of efficiency branch

Makefile Outdated
NM_CAND=( \
"$(LIND_WASM_ROOT)/clang+llvm-18.1.8-x86_64-linux-gnu-ubuntu-18.04/bin/llvm-nm" \
"$$(command -v llvm-nm || true)" \
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case of clang, ar and ranlib, if the binaries with llvm are not found, they default to the generic ones.
The question is, if we need to do that. I think in our current build system, all these tools should default to llvm specific ones and if they are not present, the error should be reported.
@m-hemmings What do you think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine with me, I can remove the fallbacks, that makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add llvm-nm to build/.toolchain.env

2 participants