qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] tests/docker: Install tools to cross-debug and build Linux kernels
Date: Thu, 5 Mar 2020 11:30:01 +0100	[thread overview]
Message-ID: <030679b1-2fb7-0687-9ac7-f2cfe4ed8b02@redhat.com> (raw)
In-Reply-To: <4481651f-1c10-ca86-dc57-02aaff7d2a1a@redhat.com>

ping ping?

On 2/24/20 1:20 PM, Philippe Mathieu-Daudé wrote:
> On 2/12/20 9:27 PM, Philippe Mathieu-Daudé wrote:
>> From: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>
>> We often run Linux kernels to test QEMU. We sometimes need
>> to build them manually to use non-default features. We only
>> miss the tiny 'bc' tool.
>>
>> The ncurses library is helpful to run 'make menuconfig'.
>>
>> Finally, gdb-multiarch allow us to debug a TCG guest when its
>> architecture is different than the host.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>>   tests/docker/dockerfiles/debian10.docker | 3 +++
>>   tests/docker/dockerfiles/debian9.docker  | 3 +++
>>   2 files changed, 6 insertions(+)
>>
>> diff --git a/tests/docker/dockerfiles/debian10.docker 
>> b/tests/docker/dockerfiles/debian10.docker
>> index 5de79ae552..2fcdc406e8 100644
>> --- a/tests/docker/dockerfiles/debian10.docker
>> +++ b/tests/docker/dockerfiles/debian10.docker
>> @@ -17,14 +17,17 @@ RUN apt update && \
>>       DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
>>       DEBIAN_FRONTEND=noninteractive eatmydata \
>>       apt install -y --no-install-recommends \
>> +        bc \
>>           bison \
>>           build-essential \
>>           ca-certificates \
>>           clang \
>>           dbus \
>>           flex \
>> +        gdb-multiarch \
>>           gettext \
>>           git \
>> +        libncurses5-dev \
>>           pkg-config \
>>           psmisc \
>>           python3 \
>> diff --git a/tests/docker/dockerfiles/debian9.docker 
>> b/tests/docker/dockerfiles/debian9.docker
>> index 8cbd742bb5..92edbbf0f4 100644
>> --- a/tests/docker/dockerfiles/debian9.docker
>> +++ b/tests/docker/dockerfiles/debian9.docker
>> @@ -17,13 +17,16 @@ RUN apt update && \
>>       DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
>>       DEBIAN_FRONTEND=noninteractive eatmydata \
>>       apt install -y --no-install-recommends \
>> +        bc \
>>           bison \
>>           build-essential \
>>           ca-certificates \
>>           clang \
>>           flex \
>> +        gdb-multiarch \
>>           gettext \
>>           git \
>> +        libncurses5-dev \
>>           pkg-config \
>>           psmisc \
>>           python3 \
>>
> 
> ping?



  reply	other threads:[~2020-03-05 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 20:27 [PATCH] tests/docker: Install tools to cross-debug and build Linux kernels Philippe Mathieu-Daudé
2020-02-24 12:20 ` Philippe Mathieu-Daudé
2020-03-05 10:30   ` Philippe Mathieu-Daudé [this message]
2020-03-06 11:51     ` Alex Bennée
2020-03-06  8:35 ` Stefano Garzarella

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=030679b1-2fb7-0687-9ac7-f2cfe4ed8b02@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --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 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).