From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9f3bbb9d30a2b549f78659e3c7b9548d75467aa3
Date: Sun, 13 Sep 2015 18:57:23 +0200 [thread overview]
Message-ID: <20150913165723.7AA05223A6@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 9f3bbb9d30a2b549f78659e3c7b9548d75467aa3 (commit)
from 11fbf1fab0a03db4c0aa37db03da9cc47d2350a8 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 9f3bbb9d30a2b549f78659e3c7b9548d75467aa3
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Sep 13 17:56:24 2015 +0100
make.sh: Fix cross-architecture builds when using the --target= parameter
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
tools/make-functions | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/tools/make-functions b/tools/make-functions
index 0152155..68ae0a1 100644
--- a/tools/make-functions
+++ b/tools/make-functions
@@ -69,7 +69,7 @@ configure_target() {
case "${target_arch}" in
x86_64)
- BUILDTARGET="${TARGET_ARCH}-unknown-linux-gnu"
+ BUILDTARGET="${target_arch}-unknown-linux-gnu"
CROSSTARGET="${BUILD_ARCH}-cross-linux-gnu"
CFLAGS_ARCH="-m64 -mtune=generic"
;;
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-09-13 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150913165723.7AA05223A6@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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