From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: Makefile: uses rsync(1), could this be optional?
Date: Fri, 21 Jan 2022 17:36:04 +0100 [thread overview]
Message-ID: <20220121163604.QqCVq%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAK7LNAQOm8NYiTDQnd0P-UsGa7GurffQiWQgGh0Cze4wLmDmgA@mail.gmail.com>
Guten Tag.
Masahiro Yamada wrote in
<CAK7LNAQOm8NYiTDQnd0P-UsGa7GurffQiWQgGh0Cze4wLmDmgA@mail.gmail.com>:
|On Fri, Jan 21, 2022 at 4:31 AM Steffen Nurpmeso <steffen@sdaoden.eu> \
|wrote:
|> I sent this to linux-kernel@vger.kernel.org on the 15th, which
|> seems to be legacy. Just in case someone is wondering about the
|> resend.
|
|I did not see your previous post.
|What is bad about using rsync?
Oh really nothing, but this Linux distribution (CRUX) recreates
Linux headers before the GNU LibC is build, and this is the only
dependency of rsync around. And, unless i am mistaken, the other
code path is more expensive but otherwise functionally equivalent?
|> As a not-yet-tested low-quality Makefile suggestion, with modern
|> GNU tools and find(1)'s -printf, wouldn't the following code work
|> out gracefully in practice? (Not subscribed.)
|>
|> Thanks for Linux!
|>
|> --- Makefile.orig 2022-01-15 19:33:59.337393371 +0100
|> +++ Makefile 2022-01-15 19:34:07.447393217 +0100
|> @@ -1260,8 +1288,17 @@ export INSTALL_HDR_PATH = $(objtree)/usr
|> quiet_cmd_headers_install = INSTALL $(INSTALL_HDR_PATH)/include
|> cmd_headers_install = \
|> mkdir -p $(INSTALL_HDR_PATH); \
|> - rsync -mrl --include='*/' --include='*\.h' --exclude='*' \
|> - usr/include $(INSTALL_HDR_PATH)
|> + if command -v rsync; then \
|> + rsync -mrl --include='*/' --include='*\.h' --exclude='*' \
|> \
|> + usr/include $(INSTALL_HDR_PATH);\
|> + else \
|> + cd usr;\
|> + find include/ -type f -name '*.h' -printf '%f %h\n' |\
|> + while read f d; do \
|> + mkdir -p $(INSTALL_HDR_PATH)/$$d;\
|> + cp -P $$d/$$f $(INSTALL_HDR_PATH)/$$d/$$f;\
|> + done;\
|> + fi
|>
|> PHONY += headers_install
|> headers_install: headers
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2022-01-21 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 19:21 Makefile: uses rsync(1), could this be optional? Steffen Nurpmeso
2022-01-21 7:12 ` Masahiro Yamada
2022-01-21 16:36 ` Steffen Nurpmeso [this message]
2022-01-23 0:50 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2022-01-15 18:40 Steffen Nurpmeso
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=20220121163604.QqCVq%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.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.