From: "Marc Hartmayer" <mhartmay@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, Thomas Huth <thuth@redhat.com>
Cc: Andrew Jones <andrew.jones@linux.dev>, kvm@vger.kernel.org
Subject: Re: [RFC kvm-unit-tests PATCH] build: fix .aux.o target building
Date: Thu, 06 Jun 2024 09:58:45 +0200 [thread overview]
Message-ID: <87h6e6sdsa.fsf@linux.ibm.com> (raw)
In-Reply-To: <D1SMM4C3H27B.2VWTDLUIB7RU3@gmail.com>
On Thu, Jun 06, 2024 at 01:49 PM +1000, "Nicholas Piggin" <npiggin@gmail.com> wrote:
> On Thu Jun 6, 2024 at 1:07 AM AEST, Marc Hartmayer wrote:
>> On Wed, Jun 05, 2024 at 08:53 PM +1000, "Nicholas Piggin" <npiggin@gmail.com> wrote:
>> > On Wed Jun 5, 2024 at 8:42 PM AEST, Marc Hartmayer wrote:
>> >> On Wed, Jun 05, 2024 at 06:16 PM +1000, Nicholas Piggin <npiggin@gmail.com> wrote:
[…snip…]
>
>
>> But what was also interesting is that if I’m using multiple
>> jobs I don’t see the issue.
>>
>> make clean -j; make -j; make -j # <- the last make has nothing to do
>>
>> if I’m using:
>>
>> make clean -j; make; make -j # <- the last make has something to do…
>> that something that irritates me
>
> This is with s390x? Maybe with parallel make, the target is getting
No, it’s a ppc64 cross-build on x86.
> rebuilt via a different prerequisite that is not a .SECONDARY target?
> Adding %.aux.o in PRECIOUS there should help in that case.
Yes, it helps - that was the reason for my fix :)
>
>> >
>> > Is it better to define explicit targets if we want to keep them, or
>> > add to .PRECIOUS? Your patch would be simpler.
>>
>> Normally, I would say without .PRECIOUS it’s cleaner, but there is
>> already a .PRECIOUS for %.so… So as Andrew has already written
>>
>> .PRECIOUS: %.so %.aux.o
>>
>> should also be fine.
>
> Okay, for a minimal fix I will do that.
>
> Thanks,
> Nick
>
--
Kind regards / Beste Grüße
Marc Hartmayer
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
prev parent reply other threads:[~2024-06-06 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:16 [RFC kvm-unit-tests PATCH] build: fix .aux.o target building Nicholas Piggin
2024-06-05 10:42 ` Marc Hartmayer
2024-06-05 10:49 ` Andrew Jones
2024-06-05 10:53 ` Nicholas Piggin
2024-06-05 15:07 ` Marc Hartmayer
2024-06-06 3:49 ` Nicholas Piggin
2024-06-06 7:58 ` Marc Hartmayer [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=87h6e6sdsa.fsf@linux.ibm.com \
--to=mhartmay@linux.ibm.com \
--cc=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=npiggin@gmail.com \
--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 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.