From: svlobanov <svlobanov@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] allow to override Makefile OS variable
Date: Tue, 11 Jan 2022 11:41:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-220@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
There is a new pull request by svlobanov against master on the mblaze repository
https://github.com/svlobanov/mblaze allow-override-OS
https://github.com/leahneukirchen/mblaze/pull/220
allow to override Makefile OS variable
Overriding OS is useful for cross-compiling if build OS and
target OS are different (e.g. build on MacOS for Linux)
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
A patch file from https://github.com/leahneukirchen/mblaze/pull/220.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-allow-override-OS-220.patch --]
[-- Type: text/x-diff, Size: 794 bytes --]
From b6bc4f3c748abac693cb0d1e865548949d2b0ff4 Mon Sep 17 00:00:00 2001
From: "Sergey V. Lobanov" <sergey@lobanov.in>
Date: Tue, 11 Jan 2022 13:34:03 +0300
Subject: [PATCH] allow to override Makefile OS variable
Overriding OS is useful for cross-compiling if build OS and
target OS are different (e.g. build on MacOS for Linux)
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
---
GNUmakefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/GNUmakefile b/GNUmakefile
index 07a0b1a..4ce8fba 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -2,7 +2,7 @@ CFLAGS?=-g -O2 -fstack-protector-strong -D_FORTIFY_SOURCE=2
override CFLAGS:=-Wall -Wno-switch -Wextra $(CFLAGS)
LDLIBS=-lrt
-OS := $(shell uname)
+OS ?= $(shell uname)
ifeq ($(OS),OpenBSD)
LOCALBASE=/usr/local
next reply other threads:[~2022-01-11 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 10:41 svlobanov [this message]
2022-01-11 11:24 ` [PR PATCH] [Closed]: " svlobanov
2022-01-11 11:24 ` svlobanov
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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-220@inbox.vuxu.org \
--to=svlobanov@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).