undefined symbols l_Lake_cli, initialize_Lake, initialize_Lake_CLI on FreeBSD
Open
Nobody has claimed this yet.
bug
P-low
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
Please put an X between the brackets as you perform the following steps:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
Build fails:
ld: error: undefined symbol: l_Lake_cli
>>> referenced by LakeMain.c
>>> ../../../.build/stage0/lib/temp/LakeMain.o.export:(_lean_main)
ld: error: undefined symbol: initialize_Lake
>>> referenced by LakeMain.c
>>> ../../../.build/stage0/lib/temp/LakeMain.o.export:(initialize_LakeMain)
ld: error: undefined symbol: initialize_Lake_CLI
>>> referenced by LakeMain.c
>>> ../../../.build/stage0/lib/temp/LakeMain.o.export:(initialize_LakeMain)
Steps to Reproduce
Regular build.
Versions
lean-4.15.0
FreeBSD 14.1
lean-4.12.0 didn't have such problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the regular build on FreeBSD 14.1 with lean-4.15.0, then inspect the generated LakeMain.c and LakeMain.o.export referenced in the linker output. Trace why l_Lake_cli, initialize_Lake, and initialize_Lake_CLI are not available during linking; done means the regular build completes without these undefined-symbol errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, compilers, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100