openwrt / openwrt/packages

lm-sensors compilation failed

Open
#17,092 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

release/24.10
Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

When I tried to compile the openwrt for my router, I encountered this error:

arm-openwrt-linux-muslgnueabi-gcc  -o prog/sensors/sensors prog/sensors/main.ro prog/sensors/chips.ro -liconv -Llib -lsensors /home/colin/openwrt/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-11.2.0_musl_eabi/lib/gcc/arm-openwrt-linux-muslgnueabi/11.2.0/../../../../arm-openwrt-linux-muslgnueabi/bin/ld: cannot find -liconv
collect2: error: ld returned 1 exit status
make[4]: *** [prog/sensors/Module.mk:43: prog/sensors/sensors] Error 1
make[4]: Leaving directory '/home/colin/openwrt/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/lm-sensors-3-6-0'
make[3]: *** [Makefile:129: /home/colin/openwrt/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/lm-sensors-3-6-0/.built] Error 2
make[3]: Leaving directory '/home/colin/openwrt/feeds/packages/utils/lm-sensors'
time: package/feeds/packages/lm-sensors/compile#0.18#0.08#0.44
    ERROR: package/feeds/packages/lm-sensors failed to build.
make[2]: *** [package/Makefile:116: package/feeds/packages/lm-sensors/compile] Error 1

It seems that there's something wrong with lm-sensors. How can I fix it?

Contributor guide

Open the contributing guide

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.

Research direction

Read feeds/packages/utils/lm-sensors and prog/sensors/Module.mk, then inspect the package compile output and the missing -liconv linker dependency. Reproduce the build with the reported target; done means the lm-sensors package compiles successfully without the linker failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.