From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] sitecopy: Fix build on non-Linux hosts
Date: Sun, 22 Jan 2012 13:59:30 +0100 [thread overview]
Message-ID: <1327237170-33859-1-git-send-email-bernhard@bwalle.de> (raw)
In-Reply-To: <20120122104930.GD12400@pengutronix.de>
The build system of sitecopy uses 'uname' to determine the operating
system for which it compiles sitecopy. However, on non-Linux hosts, this
leads to wrong results.
Fixes Darwin (tested on Mac OS 10.7 Lion).
Signed-off-by: Bernhard Walle <bernhard@bwalle.de>
---
v3: Same as v1 but with SITECOPY_CONF_ENV instead of SITECOPY_AUTOCONF and with comment.
rules/sitecopy.make | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/rules/sitecopy.make b/rules/sitecopy.make
index 44a7b8a..4434fe9 100644
--- a/rules/sitecopy.make
+++ b/rules/sitecopy.make
@@ -42,6 +42,14 @@ SITECOPY_AUTOCONF := $(CROSS_AUTOCONF_USR) \
--without-socks \
--without-gssapi
+# m4/neon/neon.m4 uses uname to check for Darwin and adds some special compiler
+# options in that case. sitecopy doesn't build host tools, so anything built
+# is for the target. We can force the target operating system to Linux. That's simpler
+# than fixing the m4/neon/neon.m4 and doesn't need autoreconf to run.
+SITECOPY_CONF_ENV := \
+ $(CROSS_ENV) \
+ ne_cv_os_uname=Linux
+
ifdef PTXCONF_SITECOPY_SFTP
SITECOPY_AUTOCONF += --enable-sftp
else
--
1.7.7.4
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-01-22 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 20:27 Bernhard Walle
2012-01-18 10:05 ` Juergen Beisert
2012-01-18 10:08 ` Bernhard Walle
2012-01-18 10:23 ` Juergen Beisert
2012-01-19 7:25 ` Bernhard Walle
2012-01-19 9:17 ` Juergen Beisert
2012-01-19 18:23 ` Bernhard Walle
2012-01-22 10:49 ` Michael Olbrich
2012-01-22 12:59 ` Bernhard Walle [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=1327237170-33859-1-git-send-email-bernhard@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
/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