From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. f29f169735ff3b431c6dc7cb50b36d0fe644163b
Date: Sat, 24 Oct 2020 09:25:38 +0000 [thread overview]
Message-ID: <4CJG0y4fZnz2xhm@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1813 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, master has been updated
via f29f169735ff3b431c6dc7cb50b36d0fe644163b (commit)
from c9f30dc9fc9932da3c0aabd83dc260a5eeac9218 (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 f29f169735ff3b431c6dc7cb50b36d0fe644163b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Oct 7 08:04:38 2020 +0000
avahi: Disable custom stack protector configuration
We already pass -fstack-protector-strong, which might be overridden
by -fstack-protector-all. We also know that SSP works in our version
of libc and do not need to link against libssp.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/avahi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/avahi b/lfs/avahi
index 6807a080d..2ed13dd44 100644
--- a/lfs/avahi
+++ b/lfs/avahi
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = avahi
-PAK_VER = 6
+PAK_VER = 7
DEPS = dbus libdaemon
@@ -82,6 +82,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
--sysconfdir=/etc \
--localstatedir=/var \
--with-avahi-user=avahi \
+ --disable-stack-protector \
--disable-qt3 \
--disable-qt4 \
--disable-qt5 \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-10-24 9:25 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=4CJG0y4fZnz2xhm@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