From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e36a7e3cf23453e2cc9d5b7db3306b2cded23b80
Date: Sat, 17 Feb 2018 13:37:09 +0000 [thread overview]
Message-ID: <20180217133709.AE1AC106D063@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1509 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 e36a7e3cf23453e2cc9d5b7db3306b2cded23b80 (commit)
from 429af17883be439db0b67d05b43ad66c9c000382 (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 e36a7e3cf23453e2cc9d5b7db3306b2cded23b80
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Feb 17 13:36:37 2018 +0000
haproxy: Link against libatomic on ARM
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/haproxy | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/lfs/haproxy b/lfs/haproxy
index 508cbb83b..02e3b25f8 100644
--- a/lfs/haproxy
+++ b/lfs/haproxy
@@ -36,6 +36,10 @@ PAK_VER = 3
DEPS = ""
+ifeq "$(BUILD_ARCH)" "armv5tel"
+ LDFLAGS += -latomic
+endif
+
###############################################################################
# Top-level Rules
###############################################################################
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-02-17 13:37 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=20180217133709.AE1AC106D063@git01.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