From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. aa81aaf83646a9cbaf07f0e5358fee66ef6e4c06
Date: Tue, 27 Oct 2020 18:24:04 +0000 [thread overview]
Message-ID: <4CLKps0Lw7z2xdJ@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1586 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 aa81aaf83646a9cbaf07f0e5358fee66ef6e4c06 (commit)
from 7e5045312cce99db4f9055f3bf08c9edf98ee243 (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 aa81aaf83646a9cbaf07f0e5358fee66ef6e4c06
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Oct 27 18:22:05 2020 +0000
suricata: Link against libatomic on armv5tel
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/suricata | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/lfs/suricata b/lfs/suricata
index e89bf1e63..d47b43d34 100644
--- a/lfs/suricata
+++ b/lfs/suricata
@@ -32,6 +32,10 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
+ifeq "$(BUILD_ARCH)" "armv5tel"
+ LDFLAGS += -latomic
+endif
+
###############################################################################
# Top-level Rules
###############################################################################
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-10-27 18:24 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=4CLKps0Lw7z2xdJ@people01.haj.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