openwrt/sdk:armsr-armv8-openwrt-23.05 builds packages for octeon.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 625
- Forks
- 103
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Description
Hi, I'm probably doing something wrong here but I'm getting strange results from the SDK image, particularly the armsr variant
FROM openwrt/sdk:armsr-armv8-openwrt-23.05
RUN echo "src-git ten64 https://gitlab.com/traversetech/ls1088firmware/ten64-openwrt-feed.git^9674072" >> feeds.conf.default
RUN sed -i "s/git.openwrt.org\/feed/github.com\/openwrt/" feeds.conf.default
RUN sed -i "s/git.openwrt.org\/project/github.com\/openwrt/" feeds.conf.default
RUN sed -i "s/git.openwrt.org/github.com/" feeds.conf.default
RUN scripts/feeds update -a
#RUN scripts/feeds install -a
RUN echo CONFIG_TARGET_armsr_armv8=y >> .config
RUN echo CONFIG_TARGET_DEVICE_armsr_armv8_DEVICE_generic=y >> .config
RUN make defconfig
RUN scripts/feeds install hwmon-traverse-sensors
RUN make package/hwmon-traverse-sensors/compile -j8
#RUN sed -i s/CONFIG_ALL_KMODS=y/CONFIG_ALL_KMODS=n/ .config
#CONFIG_ALL=y
#RUN sed -i s/CONFIG_SIGNED_PACKAGES=y/CONFIG_SIGNED_PACKAGES=n/ .config
#RUN make package/hwmon-traverse-sensors/compile -j1 V=s
#RUN make package/hwmon-traverse-sensors/compile -j8
#RUN make package/index
If you run a shell from the built image, everything's in bin/targets/octeontx - shouldn't this be something similar to bin/targets/armsr?
Contributor guide
No contributing guide indexed for this repository
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 Dockerfile steps using openwrt/sdk:armsr-armv8-openwrt-23.05, then inspect feeds.conf.default, .config, and the generated bin/targets directory. Compare the selected armsr configuration with the resulting octeontx path and document whether the image or configuration selects the wrong target; done means the target output is explained or corrected and the package build still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100