From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 15374 invoked from network); 26 Jul 2021 00:14:57 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 26 Jul 2021 00:14:57 -0000 Received: (qmail 5273 invoked by uid 550); 26 Jul 2021 00:14:54 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 5252 invoked from network); 26 Jul 2021 00:14:53 -0000 Date: Sun, 25 Jul 2021 20:14:40 -0400 From: Rich Felker To: Rob Landley Cc: musl@lists.openwall.com Message-ID: <20210726001440.GO13220@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] FYI: llvm-musl-hexagon toolchain build script v1 On Sun, Jul 25, 2021 at 07:11:43PM -0500, Rob Landley wrote: > Note the first three lines are the 3 git archives to clone into the current > directory. (llvm, linux, and qualcomm's musl-hexagon fork) > > Loosely based on the > https://github.com/qemu/qemu/blob/master/tests/docker/dockerfiles/debian-hexagon-cross.docker.d/build-toolchain.sh > with a _LOT_ of simplification. Yes, it can still be slimmed down further, > working on it ala > https://lists.nongnu.org/archive/html/qemu-devel/2021-07/msg04610.html > > I built a toybox binary which qemu-hexagon could run, and I built a > comet_defconfig vlinux which... doesn't seem to have a qemu-system-hexagon board > emulation yet? Hmmm... > > Their musl hexagon branch is a couple dozen patches on top of a commit from > January of this year. Should rebase reasonnably to current without too much effort. Yes, it was proposed here a while back after a long time of being something done independently that we hadn't seen. I need to look back at the thread to determine where things are with getting it upstreamable. My lack of tooling to build and test it is partly a blocker, so if you're willing to help with that side of things it'd be great. Rich