[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 26 Sep 2023 12:55:30 -0500
From: Rob Landley <rob@...dley.net>
To: Brian Cain <bcain@...cinc.com>,
"musl@...ts.openwall.com" <musl@...ts.openwall.com>,
"Matheus Bernardino (QUIC)" <quic_mathbern@...cinc.com>
Cc: Sid Manning <sidneym@...cinc.com>, Rich Felker <dalias@...c.org>,
Fangrui Song <i@...kray.me>, Szabolcs Nagy <nsz@...t70.net>
Subject: Re: [RFC PATCH 0/5] Add support to Hexagon DSP
On 9/26/23 11:48, Brian Cain wrote:
>> -----Original Message-----
>> From: Rob Landley <rob@...dley.net>
> ...
>> On 8/30/23 07:22, Matheus Tavares Bernardino wrote:
>> > Hi,
>> >
>> > I'd like to restart the conversations from
>> > https://marc.info/?l=musl&w=2&r=1&s=Hexagon+DSP+support&q=b about
>> > adding Hexagon support to musl.
>> >
>> > I've read the comments from the two previous iterations and it looks
>> > like Sid has addressed them all already (please let me know if there is
>> > something missing, though). So I've only rebased/reorganized the patches
>> > with minor cleanup changes.
>> >
>> > These patches are also available at my git tree:
>> > https://github.com/quic/musl/tree/mathbern/to-upstream
>>
>> Is there a current toolchain build script for hexagon? I harvested an
>
> The recipe for the toolchain build is maintained here https://github.com/quic/toolchain_for_hexagon/ - along with binary releases of the toolchain itself for those who don't care to build their own.
Cloned. Let's see... The README.maryland has no usage instructions. Let's try...
$ ./build-toolchain.sh
++ date +%Y_%b_%d
+ STAMP=2023_Sep_26
+ set -euo pipefail
+ set -x
+ set +x
./build-toolchain.sh: line 250: TOOLCHAIN_INSTALL: unbound variable
$ TOOLCHAIN_INSTALL="$PWD"/walrus ./build-toolchain.sh
++ date +%Y_%b_%d
+ STAMP=2023_Sep_26
+ set -euo pipefail
+ set -x
+ set +x
./build-toolchain.sh: line 256: ROOT_INSTALL: unbound variable
The ./build-rootfs.sh has functions to compile busybox and dropbear, don't want
to go there right now...
Let's see, build-toolchain.sh starts with multiple large function definitions,
let's jump to the end... tarring stuff up, and before that it iterates "for t in
${CROSS_TRIPLES}" which is:
CROSS_TRIPLES="aarch64-windows-gnu x86_64-windows-gnu aarch64-linux-gnu
aarch64-macos"
CROSS_TRIPLES=""
It blanks it right after setting it. Great. And none of those look interesting.
(No x86-64 linux...)
Ok, before spelunking farther I'll ask: what is the expected invocation here?
Rob
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
