qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] config-host.mak: remove unused compiler-related lines
Date: Tue, 6 Jul 2021 10:09:28 +0200	[thread overview]
Message-ID: <c4d3516a-5788-fec5-c8fc-2051c9f46a50@redhat.com> (raw)
In-Reply-To: <e53e0e67-a508-84af-70cf-552154b3501a@redhat.com>

On 06/07/21 09:37, Thomas Huth wrote:
> 
> I wasn't quite sure whether we'd still need some of those e.g. for 
> compiling capstone or dtc, but looking at meson.build again, I think 
> you're right, we're not using "make" to build those anymore, right?

Yeah, only the ROMs are built via makefiles (I'd like to reuse the 
tests/tcg machinery for them as well, but not yet).  Also 
config-host.mak is not used in submodules such as SLOF or u-boot, so 
those are safe too.

Thanks,

Paolo

> In that case:
> 
> Reviewed-by: Thomas Huth <thuth@redhat.com>



      reply	other threads:[~2021-07-06  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  7:29 [PATCH] config-host.mak: remove unused compiler-related lines Paolo Bonzini
2021-07-06  7:37 ` Thomas Huth
2021-07-06  8:09   ` Paolo Bonzini [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=c4d3516a-5788-fec5-c8fc-2051c9f46a50@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).