Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

编译libTinyNN.so 缺少文件version.ld

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cmake, cpp, python

Research direction

Start with runtime/scripts/runtime_build.py and the CMake/Ninja build invoked for the runtime directory, then trace why runtime/version.ld is required for libTinyNN.so but is absent. Reproduce the reported ninja install/strip failure and confirm the runtime build completes with libTinyNN.so produced.

Written by the indexing model from the issue text.

Description

报这个错误
2023/08/25 15:43:04 - DEBUG - cmake build: cd /home/work/wanxin/megcc_root_release/release_megcc/yolox_example/kernel_yolox_s_arm_v2/runtime && ninja install/strip
ninja: error: '/home/work/wanxin/megcc_root_release/release_megcc/runtime/version.ld', needed by 'libTinyNN.so', missing and no known rule to make it
Traceback (most recent call last):
File "/home/work/wanxin/megcc_root_release/release_megcc/yolox_example/../runtime/scripts/runtime_build.py", line 424, in
b.build()
File "/home/work/wanxin/megcc_root_release/release_megcc/yolox_example/../runtime/scripts/runtime_build.py", line 415, in build
subprocess.check_call('bash -c "{}"'.format(build_cmd), shell=True)
File "/home/work/miniconda3/envs/wx_mge_env/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'bash -c "cd /home/work/wanxin/megcc_root_release/release_megcc/yolox_example/kernel_yolox_s_arm_v2/runtime && ninja install/strip "' returned non-zero exit status 1.

Dominant language
C++
Stars
483
Forks
56
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MegEngine/MegCC

All issues in MegEngine/MegCC

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.