big endian ppc builds are broken
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 3
Description
In GitLab by @nickdesaulniers on Dec 21, 2020, 21:04 GMT:
See for example: https://builds.tuxbuild.com/1liBNF6Jmycwvmc6DXUPeX4OB4p/build.log
It looks like powerpc64le-linux-gnu- is always used for the target triple, which will error when building for big endian targets (such as ppc44x_defconfig or pseries_defconfig). I suspect mips has a similar issue, where the arch is bi-endian and the target triple is must match the config).
For example, we might do the following builds:
$ ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- make CC=clang -j powernv_defconfig
$ ARCH=powerpc CROSS_COMPILE=powerpc64-linux-gnu- make CC=clang -j pseries_defconfig
$ ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- make CC=clang -j ppc44x_defconfig
Migrated from GitLab: https://gitlab.com/Linaro/tuxmake/-/issues/108
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
Start by tracing how TuxMake selects the target triple for the listed powerpc builds, using the powernv_defconfig, pseries_defconfig, and ppc44x_defconfig command examples as entry points. Reproduce the failure with the big-endian configurations and verify that each configuration uses a matching triple without breaking the little-endian build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100