All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/Makefile.in: only error out when no C library is configured when building
Date: Sat, 17 Sep 2022 11:59:49 +0200	[thread overview]
Message-ID: <877d2248yy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220821190153.233016-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Sun, 21 Aug 2022 21:01:52 +0200")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > Commit fda53f0791f5657d41735a40a29df3c8d0e8ae79 ("package/Makefile.in:
 > add detection for the lack of C library") added an $(error ...)
 > message when no C library is available for the currently selected
 > architecture.

 > However, this error message pops up not just when building, so for
 > example, the command:

 >   make BR2_HAVE_DOT_CONFIG=y VARS=%_LICENSE printvars

 > no longer works (this command is used by the pkg-stats script).

 > We restore a functional behavior by doing the check only when
 > BR_BUILDING=y.

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2022.05.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-09-17  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 19:01 [Buildroot] [PATCH] package/Makefile.in: only error out when no C library is configured when building Thomas Petazzoni via buildroot
2022-08-21 19:31 ` Yann E. MORIN
2022-09-17  9:59 ` Peter Korsgaard [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=877d2248yy.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --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.