Closed juanique closed 2 months ago
I just saw that this is documented here: https://www.kcl-lang.io/docs/user_docs/support/faq-install#errors-on-startingrunning-kcl-inside-a-container-for-permission-denied-or-file-not-found
But I want to say this seem like such an unnecessary requirement. This is just a config builder tool, it should be a simple binary that you can run with all requirements precompiled. There's no reason to build C++ code during runtime.
You can set the env KCL_FAST_EVAL=1 to prevent the ld deps in the 0.10.0
Released v0.10.0-beta.1 and close it.
Bug Report
KCL cli does not work for me, it fails with
Error: run linker failed: stdout , stderr: collect2: fatal error: cannot find 'ld'
Why does it need a linker? I just want to run the example from the codelab: https://www.kcl-lang.io/docs/reference/lang/codelab/simple
I cannot install a C++ toolchain on this machine
1. Minimal reproduce step (Required)
ld
installed in the system path2. What did you expect to see? (Required)
After running the command
kcl my_config.k
from the codelab I expected the config to be built.3. What did you see instead (Required)
4. What is your KCL components version? (Required)
v.0.9.7 from https://github.com/kcl-lang/cli/releases/download/v0.9.7/kcl-v0.9.7-linux-amd64.tar.gz