3 ms·
Ah, thanks! I dug a little more and found that the original test [1] from llvm-toolchain was a little different in the upstream Debian repository. It set the
by opello 3y ago
Ah, thanks! I dug a little more and found that the original test [1] from llvm-toolchain was a little different in the upstream Debian repository. It set the triple to armv7l for armhf hosts.
But I haven't yet found a similar repository on the Raspbian side. I guess I'd expect to find it within their GitHub org, but my searching didn't reveal it.
[1] https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/af56187b7d04d718f3f2229691885b102bb026a5 https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/comm...
- orra 3y agoYeah, Raspbian doesn't seem to be developed as a community project. There's no package tracker[1] like Debian or Ubuntu. I suppose they don't tend to diverge much, in practice. Anyway, I suppose this all means Raspberry Pi OS/Raspbian are able to patch this, without requiring it to first be fixed in Debian or Clang. [1] https://raspberrypi.stackexchange.com/questions/1179/does-raspbians-repository-have-a-browsable-package-list https://raspberrypi.stackexchange.com/questions/1179/does-ra...
- opello 3y agoInteresting. Uncovering this slight difference really makes me long for something like the Debian GitLab instance (or really any kind of public change tracking) to document a bug or suggest a change. Agreed, sure looks like it's Raspbian's build configuration to fix.
- aragilar 3y agoYou can also use https://raspi.debian.net/ https://raspi.debian.net/, which is preferable on newer Pis due to the use of arm64 (early Pis had a weird arch which sat between armel and armhf, so either you used armel and things were slow(er), or you rebuilt the packages with the extra float support (as Raspbian did)).