All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Markus Mayer <mmayer@broadcom.com>
Cc: Markus Mayer via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] Makefile: set HOST*_NOCCACHE variables only if unset
Date: Tue, 28 Dec 2021 22:26:35 +0100	[thread overview]
Message-ID: <3e2a86be-e5d5-a4e4-1be8-e263c20b0a5f@green-communications.fr> (raw)
In-Reply-To: <20211228221804.6b965558@windsurf>

On 28/12/2021 22:18, Thomas Petazzoni wrote:
> On Tue, 28 Sep 2021 12:55:33 -0700
> Markus Mayer via buildroot <buildroot@buildroot.org> wrote:
> 
>> Set HOSTCC_NOCCACHE and HOSTCXX_NOCCACHE only if they are not set. This
>> allows recursive calls to "make" to work as intended in the presence of
>> ccache.
>>
>> Without guarding these variables, a recursive invocation of make would
>> re-define
> 
> What is the use-case for a recursive invocation of make, reparsing the
> Buildroot Makefile?

The cover text mentions it: calling make legal-info inside a post-build 
script (or package, actually) to somehow include the result in the image.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-28 21:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 19:55 [Buildroot] [PATCH 0/1] Build issue related to "command -v" Markus Mayer via buildroot
2021-09-28 19:55 ` [Buildroot] [PATCH 1/1] Makefile: set HOST*_NOCCACHE variables only if unset Markus Mayer via buildroot
2021-09-29 19:27   ` Petr Vorel
2021-12-28 21:18   ` Thomas Petazzoni
2021-12-28 21:26     ` Nicolas Cavallari [this message]
2021-12-29  9:00       ` Thomas Petazzoni
2021-12-29  9:12   ` Thomas Petazzoni
2021-09-29  8:24 ` [Buildroot] [PATCH 0/1] Build issue related to "command -v" Nicolas Cavallari
2021-09-29 16:14   ` David Laight
2021-09-29 17:30     ` Petr Vorel
2021-09-29 19:59 ` Arnout Vandecappelle
2021-09-29 20:11   ` Petr Vorel
2021-10-01 17:53     ` Markus Mayer via buildroot
2021-10-01 18:17       ` Yann E. MORIN
2021-10-02 19:23         ` Petr Vorel

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=3e2a86be-e5d5-a4e4-1be8-e263c20b0a5f@green-communications.fr \
    --to=nicolas.cavallari@green-communications.fr \
    --cc=buildroot@buildroot.org \
    --cc=mmayer@broadcom.com \
    --cc=thomas.petazzoni@bootlin.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.