mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
	 David Dgien <dgienda125@gmail.com>
Subject: Re: [PATCH] kbuild: Use uname for BAREBOX_COMPILE_HOST
Date: Mon, 03 Feb 2025 10:18:17 +0100	[thread overview]
Message-ID: <173857429720.3522156.14761012076799558840.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250131-hostname-fix-v1-1-8d7ae619fcf4@gmail.com>


On Fri, 31 Jan 2025 22:59:08 -0500, David Dgien wrote:
> Adoption of Linux Commit:
> 
> | commit 1e66d50ad3a1dbf0169b14d502be59a4b1213149
> | Author: Chris Down <chris@chrisdown.name>
> | Date:   Tue Oct 20 10:34:59 2020 +0100
> |
> |     kbuild: Use uname for LINUX_COMPILE_HOST detection
> |
> |     `hostname` may not be present on some systems as it's not mandated by
> |     POSIX/SUSv4. This isn't just a theoretical problem: on Arch Linux,
> |     `hostname` is provided by `inetutils`, which isn't part of the base
> |     distribution.
> |
> |         ./scripts/mkcompile_h: line 38: hostname: command not found
> |
> |     Use `uname -n` instead, which is more likely to be available (and
> |     mandated by standards).
> |
> |     Signed-off-by: Chris Down <chris@chrisdown.name>
> |     Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> 
> [...]

Applied, thanks!

[1/1] kbuild: Use uname for BAREBOX_COMPILE_HOST
      https://git.pengutronix.de/cgit/barebox/commit/?id=b001dfee2bd0 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      reply	other threads:[~2025-02-03  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-01  3:59 David Dgien via B4 Relay
2025-02-03  9:18 ` Sascha Hauer [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=173857429720.3522156.14761012076799558840.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=dgienda125@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox