mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
	linux-kernel@vger.kernel.org, Willy Tarreau <w@1wt.eu>
Subject: [PATCH 0/3] tools/nolibc: fix build issues when building from tools/
Date: Sat, 28 May 2022 17:45:43 +0200	[thread overview]
Message-ID: <20220528154546.8261-1-w@1wt.eu> (raw)

Hi,

Linus reported build issues when trying nolibc according to the
documented procedure in "make tools/help":

  https://lore.kernel.org/lkml/CAHk-=wgpAHhPVSqBWb4gYT=CRJzKAZ4inmrL_kcpeNWGkcg3pg@mail.gmail.com/

This series addresses this by setting the ARCH and OUTPUT variables and
adding a few targets to match default expectations. A "help" target also
explains what the existing targets do. This will be particularly useful
once the test suite is merged since it will add new targets.

Thanks,
Willy

---
Willy Tarreau (3):
  tools/nolibc: fix the makefile to also work as "make -C tools ..."
  tools/nolibc: make the default target build the headers
  tools/nolibc: add a help target to list supported targets

 tools/Makefile                |  3 +++
 tools/include/nolibc/Makefile | 37 +++++++++++++++++++++++++++++++++--
 2 files changed, 38 insertions(+), 2 deletions(-)

-- 
2.17.5


             reply	other threads:[~2022-05-28 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28 15:45 Willy Tarreau [this message]
2022-05-28 15:45 ` [PATCH 1/3] tools/nolibc: fix the makefile to also work as "make -C tools ..." Willy Tarreau
2022-05-28 15:45 ` [PATCH 2/3] tools/nolibc: make the default target build the headers Willy Tarreau
2022-05-28 15:45 ` [PATCH 3/3] tools/nolibc: add a help target to list supported targets Willy Tarreau
2022-05-31 15:23 ` [PATCH 0/3] tools/nolibc: fix build issues when building from tools/ Paul E. McKenney

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=20220528154546.8261-1-w@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®