-----Original Message-----
From: Randy Dunlap <redacted>

...

quoted

Randy,

	I 100% agree, I would prefer a tarball myself.  I have been working with

the team to produce the tarball and we haven't been able to deliver that yet.
No good excuses here, only bad ones: somewhat tied up in process
bureaucracy.

quoted

I can share the recipe that was used to build the toolchain in the container.

No Dockerfile required, just a shell script w/mostly cmake + make commands.
All of the sources are public, but musl is a downstream-public repo because we
haven't landed the hexagon support in upstream musl yet.

Hi Brian,
I can wait. :)

Randy, thanks for your patience.  We don't quite have all the kinks worked out for a release process but I have worked with the Linaro team to produce a clang-based cross toolchain and we can share a link:

https://codelinaro.jfrog.io/artifactory/codelinaro-qemu/2021-05-12/clang+llvm-12.0.0-cross-hexagon-unknown-linux-musl.tar.xz

Contents:
- clang+llvm+lld+libunwind+libcxx+libcxxabi built from `llvmorg-12.0.0` release
- `qemu-hexagon` binary (scalar core only!) built from upstream github.com/qemu/qemu repo `15106f7dc3290ff3254611f265849a314a93eb0e`
- headers from linux kernel 5.6.18
- C library built from github.com/quic/musl commit aff74b395fbf59cd7e93b3691905aa1af6c0778c
- unabridged build details in https://github.com/quic/qemu/tree/d26f3843c794d9d9b17b637550dc3b5a2bacd837/quic/container

Once we're able to produce releases on a more regular basis we should be able to share a hexagon-linux-user QEMU that can do scalar+vector.  And some time after that a sysemu-capable qemu.

Our process for this first run did not include a signature for the build tarball, and that is regrettable.  It will be included next time around.  I have produced the sha256 signature below (post hoc) of the tarball that I tested:

	55c51e8289cc21e6779cfc3b18bb9ad02632fc52d3c3a91bf6fdb4c8f578c84c  clang+llvm-12.0.0-cross-hexagon-unknown-linux-musl.tar.xz

-Brian