From: Richard Henderson <richard.henderson@linaro.org>
To: "Brian Cain" <bcain@quicinc.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Taylor Simpson <tsimpson@quicinc.com>
Subject: Re: hexagon container update
Date: Fri, 1 Oct 2021 13:23:43 -0400 [thread overview]
Message-ID: <107df921-3339-7b73-15f3-daba2d61882e@linaro.org> (raw)
In-Reply-To: <SN6PR02MB42057F473618E661B72E1FF3B8AB9@SN6PR02MB4205.namprd02.prod.outlook.com>
On 10/1/21 12:59 PM, Brian Cain wrote:
> Alex,
>
> We need to update the docker container used for hexagon for new test cases proposed in Taylor's recent patch series under review. Thankfully, CodeLinaro has provided a binary of the hexagon cross toolchain so now I think we can simplify the hexagon docker file to something like the below. I hope this also means that we can remove the exceptional handling for the hexagon container.
>
> I can propose a patch but I'm not quite certain how to test it.
make docker-image-debian-hexagon-cross NOCACHE=1 V=1
and then make check-tcg to use the new image.
>
> The "--no-check-certificate" argument to wget is very bad but I'm not quite certain how to upgrade/change the container's certificate store to accept the apparently-legit-but-perhaps-newer-than-expected certificate presented by codelinaro.jfrog.io.
Hum. This all suggests that it would be better to update the build-toolchain script.
> RUN cd /tmp && \
> wget --quiet --no-check-certificate ${CLANG_URL}
> RUN cd /opt && \
> tar xf /tmp/clang+llvm-Sept-2021-cross-hexagon-unknown-linux-musl.tar.xz
You'd want to remove the tarball as well.
r~
next prev parent reply other threads:[~2021-10-01 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 16:59 hexagon container update Brian Cain
2021-10-01 17:23 ` Richard Henderson [this message]
2021-10-01 17:59 ` Brian Cain
2021-10-01 21:44 ` Alex Bennée
2021-10-02 0:22 ` Brian Cain
2022-01-15 3:36 ` Brian Cain
2022-01-17 14:47 ` Alex Bennée
2022-01-18 15:25 ` Brian Cain
2022-01-18 15:41 ` Brian Cain
2021-10-02 13:09 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=107df921-3339-7b73-15f3-daba2d61882e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bcain@quicinc.com \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).