Sorted now. I had applied the patch but was running into trouble because
although I'd pushed to the project registry when running on my gitlab
project it was using the personal registry. Will post v3 later today.
On Tue, 11 May 2021, 16:08 Brian Cain, wrote:
> > -Original Message-
> >
> -Original Message-
> From: Brian Cain
...
> > I suspect the easiest thing to do is to drop the patches again so I
> > don't hold up the rest of testing/next. I can include the initial
> > docker image patch but I won't enable it in configure.sh/gitlab.
>
> Sorry -- I sent along a patch
> -Original Message-
> From: Alex Bennée
...
> Which leads to the compiler complaining:
>
> hexagon-unknown-linux-musl-clang -Wno-incompatible-pointer-types -
> Wno-undefined-internal -fno-unroll-loops -Wall -Werror -O0 -g -fno-strict-
> aliasing -mv67 -O2 -static /home
>
Alex Bennée writes:
> We special case this as the container with the cross compiler for the
> tests takes so long to build it is manually uploaded into the
> registry.
Gahh, something changed underneath me with the inclusion of:
commit 46ef47e2a77d1a34996964760b4a0d2b19476f25
Author:
On 4/19/21 4:54 PM, Alex Bennée wrote:
> We special case this as the container with the cross compiler for the
> tests takes so long to build it is manually uploaded into the
> registry.
>
> Signed-off-by: Alex Bennée
> Reviewed-by: Philippe Mathieu-Daudé
> Reviewed-by: Wainer dos Santos
On Mon, Apr 19, 2021 at 11:54 AM Alex Bennée wrote:
>
> We special case this as the container with the cross compiler for the
> tests takes so long to build it is manually uploaded into the
> registry.
>
> Signed-off-by: Alex Bennée
> Reviewed-by: Philippe Mathieu-Daudé
> Reviewed-by: Wainer
We special case this as the container with the cross compiler for the
tests takes so long to build it is manually uploaded into the
registry.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Wainer dos Santos Moschetta
Message-Id:
