All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Orzel, Michal" <michal.orzel@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>
Subject: Re: [PATCH] tests/vpci: Use $(CC) instead of $(HOSTCC)
Date: Mon, 2 Jun 2025 17:40:01 +0200	[thread overview]
Message-ID: <5c58a036-2dae-4b12-97a1-e2fbafea4999@amd.com> (raw)
In-Reply-To: <e3f4b507-5f66-47f4-bffd-6cfda48bea3f@citrix.com>



On 02/06/2025 17:36, Andrew Cooper wrote:
> On 02/06/2025 4:09 pm, Michal Orzel wrote:
>> These tests are supposed to run on target. HOSTCC can be different than
>> CC (when cross-compiling). At the moment, tests installation would put
>> a binary of a wrong format in the destdir.
>>
>> Fixes: e90580f25bd7 ("vpci: introduce basic handlers to trap accesses to the PCI config space")
>> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
> 
> Oh.  This didn't explode in GitlabCI because there's no ARM version of
> *-tools-tests-*.
> 
> Can we fix that too please, seeing as there is a real ARM board?
We will add it to our TODO.

> 
> Also, I guess we have to finally sort out the CC vs HOSTCC debate.
> 
> ~Andrew

~Michal



  reply	other threads:[~2025-06-02 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 15:09 [PATCH] tests/vpci: Use $(CC) instead of $(HOSTCC) Michal Orzel
2025-06-02 15:36 ` Andrew Cooper
2025-06-02 15:40   ` Orzel, Michal [this message]
2025-06-02 15:50   ` Jan Beulich
2025-06-02 16:00     ` Andrew Cooper
2025-06-03  6:41     ` Orzel, Michal
2025-06-03  6:46 ` Roger Pau Monné
2025-06-03  6:52   ` Orzel, Michal
2025-06-03 10:30     ` Roger Pau Monné
2025-06-03 11:23       ` Orzel, Michal

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=5c58a036-2dae-4b12-97a1-e2fbafea4999@amd.com \
    --to=michal.orzel@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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.