All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PATCH] tests/docker: Use binaries for debian-tricore-cross
Date: Fri, 03 Feb 2023 15:52:00 +0000	[thread overview]
Message-ID: <87o7qakapc.fsf@linaro.org> (raw)
In-Reply-To: <c21d19e6-7e8a-a66e-0c65-f05954e429d7@linaro.org>


Philippe Mathieu-Daudé <philmd@linaro.org> writes:

> Hi Bastian,
>
> On 3/2/23 15:54, Bastian Koppelmann wrote:
>> since binutils is pretty old, it fails our CI repeatedly during the
>> compilation of tricore-binutils. We created a precompiled version using
>> the debian docker image and download it instead of building it ourself.
>> Signed-off-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
>> ---
>> Peter, I was having trouble with the new version of binutils, I mentioned. I
>> think this needs more time to sort out. So for now, let's just use a precompiled
>> version of the current binutils.
>>   .../dockerfiles/debian-tricore-cross.docker    | 18
>> +++---------------
>>   1 file changed, 3 insertions(+), 15 deletions(-)
>> diff --git a/tests/docker/dockerfiles/debian-tricore-cross.docker
>> b/tests/docker/dockerfiles/debian-tricore-cross.docker
>> index 5ae58efa09..4abcf07e68 100644
>> --- a/tests/docker/dockerfiles/debian-tricore-cross.docker
>> +++ b/tests/docker/dockerfiles/debian-tricore-cross.docker
>> @@ -16,32 +16,20 @@ MAINTAINER Philippe Mathieu-Daudé <f4bug@amsat.org>
>>   RUN apt update && \
>>       DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
>>       DEBIAN_FRONTEND=noninteractive eatmydata apt install -yy \
>> -       bison \
>> +       curl \
>>          bzip2 \
>>          ca-certificates \
>> -       ccache \
>
> You might not use ccache, but others do, so please let it:
>
> $ git grep DOCKER_CCACHE
> tests/docker/Makefile.include:203:DOCKER_CCACHE_DIR :=
> $$HOME/.cache/qemu-docker-ccache
> tests/docker/Makefile.include:212:      @mkdir -p "$(DOCKER_CCACHE_DIR)"
> tests/docker/Makefile.include:234:                              -v
> $(DOCKER_CCACHE_DIR):/var/tmp/ccache:z \
>
>> -       flex \
>> -       g++ \
>> -       gcc \
>> -       git \
>>          libglib2.0-dev \
>>          libpixman-1-dev \
>>          locales \
>> -       make \
>
> Why remove gcc/(git)/make?

In retrospect 39ce923732 (gitlab: enable a very minimal build with the
tricore container) could have made the minimal qemu build requirements
clearer in the comment text at the top of the container.

>
>>          ninja-build \
>>          pkgconf \
>>          python3-pip \
>>          python3-setuptools \
>>          python3-wheel
>>   -RUN git clone --single-branch \
>> -        https://github.com/bkoppelmann/tricore-binutils.git \
>> -        /usr/src/binutils && \
>> -    cd /usr/src/binutils && chmod +x missing && \
>> -    CFLAGS=-w ./configure --prefix=/usr/local --disable-nls --target=tricore && \
>> -    make && make install && \
>> -    rm -rf /usr/src/binutils
>> -
>> +RUN curl -#SL https://github.com/bkoppelmann/tricore-binutils/raw/master/release/tricore-binutils.2.13.tar.gz \
>> +    | tar -xzC /usr/local/
>>   # This image can only build a very minimal QEMU as well as the tests
>>   ENV DEF_TARGET_LIST tricore-softmmu
>>   ENV QEMU_CONFIGURE_OPTS --disable-user --disable-tools --disable-fdt


-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2023-02-03 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 14:54 [PATCH] tests/docker: Use binaries for debian-tricore-cross Bastian Koppelmann
2023-02-03 15:02 ` Philippe Mathieu-Daudé
2023-02-03 15:36   ` Bastian Koppelmann
2023-02-03 15:52   ` Alex Bennée [this message]

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=87o7qakapc.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.