> -----Original Message----- > From: Brian Cain ... > > -----Original Message----- > > From: Richard Henderson <richard.hender...@linaro.org> > ... > > 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. > > Ok -- so the intent of the NOCACHE is that it will force the use of my newly > modified Dockerfile and not the one in the qemu container repository?
Ok, I did this. It succeeded but I don't know how to connect the dots to verify that I was indeed using the new container. Below is an excerpt of what I saw when I did the build of the attached patch. And also attached is the subsequent check-tcg (which succeeded). ~~~~~~~~~~~~~~ .... wget 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 902 kB of archives. After this operation, 3335 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian buster/main amd64 wget amd64 1.20.1-1.1 [902 kB] Fetched 902 kB in 0s (6882 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package wget. (Reading database ... 31442 files and directories currently installed.) Preparing to unpack .../wget_1.20.1-1.1_amd64.deb ... Unpacking wget (1.20.1-1.1) ... Setting up wget (1.20.1-1.1) ... Processing triggers for man-db (2.8.5-2) ... 5f9c7fa86eccc67cd728c0abb7b9594a07d1b1352cef34071fe4e6b64b1490a0 STEP 3: ENV TOOLCHAIN_INSTALL /usr/local 1ab2399cec0fb86c7dc9dc285624fb9ac3ab8c3003771019adeb119340e447fa STEP 4: ENV ROOTFS /usr/local 43d148dd8c05e2e15cff0a17c2ad4eabd787f8d510a88750068baa300b396d4c STEP 5: ENV CLANG_URL https://codelinaro.jfrog.io/artifactory/codelinaro-toolchain-for-hexagon/v2021.09.10/clang+llvm-Sept-2021-cross-hexagon-unknown-linux-musl.tar.xz 509096591e3bac18547a0920e607568b83d451f729e855f23b3a2e99fc7a909f STEP 6: RUN cd /tmp && wget --quiet ${CLANG_URL} && cd ${TOOLCHAIN_INSTALL} && tar xf /tmp/clang+llvm-Sept-2021-cross-hexagon-unknown-linux-musl.tar.xz && rm /tmp/clang+llvm-Sept-2021-cross-hexagon-unknown-linux-musl.tar.xz 9dee02ab62a00f1d01dd67d6d2feb79756a2a6d87522939ae65fc78dc2188b41 STEP 7: LABEL com.qemu.dockerfile-checksum=c0890fe4ecc53a1d1d03e57bc44db32033c7aa75 a6127bcadaf0a1a50323e091400351046fc86ccf732189df2537ab119abdeec8 STEP 8: LABEL com.qemu./home/brian/src/qemu/tests/docker/dockerfiles/debian-hexagon-cross.docker.d/build-toolchain.sh-checksum=a032ac0a66c02f586b1c1d9476c6d4cced9f8d1a STEP 9: COMMIT qemu/debian-hexagon-cross 2acafd2af1be90a2491fcf6445a64674d1fd7b146c1487d6784942145e7f3d65 $ podman image ls|grep hexagon-cross localhost/qemu/debian-hexagon-cross latest 81492ed2e4c1 4 months ago 3.3 GB registry.gitlab.com/qemu-project/qemu/qemu/debian-hexagon-cross latest 81492ed2e4c1 4 months ago 3.3 GB localhost/qemu debian-hexagon-cross 779040354471 14 months ago 2.32 GB $ podman image ls|head REPOSITORY TAG IMAGE ID CREATED SIZE <none> <none> ca368e4baacb About an hour ago 3.3 GB <none> <none> f67f015ae642 About an hour ago 3.3 GB <none> <none> 823263f1f065 About an hour ago 3.3 GB <none> <none> 2acafd2af1be About an hour ago 2.56 GB ~~~~~~~~~ > > > 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. > > If there's any trust concerns we can verify the download in the dockerfile > using > the hash file for the tarball and/or the gpg signature. This looks like it's moot, maybe due to some system or proxy [mis]configuration. I moved to another system and didn't encounter the certificate issue.
check_tcg.log
Description: check_tcg.log
0001-Hexagon-cross-tools-docker-image-update.patch
Description: 0001-Hexagon-cross-tools-docker-image-update.patch
