From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 277060a472c826541885b40392e0d5a96ba1cf97
Date: Tue, 07 Jan 2014 16:16:35 +0100 [thread overview]
Message-ID: <20140107151636.46E9F205A3@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1825 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, fifteen has been updated
via 277060a472c826541885b40392e0d5a96ba1cf97 (commit)
from 5ca9ea6a28511653ca1c6d42725c15723ef89104 (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 277060a472c826541885b40392e0d5a96ba1cf97
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Jan 7 16:14:30 2014 +0100
mysql: Fix compiling with -fno-strict-aliasing.
-----------------------------------------------------------------------
Summary of changes:
lfs/mysql | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/mysql b/lfs/mysql
index 5fcd7b3..aa5c357 100644
--- a/lfs/mysql
+++ b/lfs/mysql
@@ -32,7 +32,9 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = mysql
-PAK_VER = 2
+PAK_VER = 3
+
+CFLAGS += -fno-strict-aliasing
###############################################################################
# Top-level Rules
@@ -75,7 +77,6 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
- cd $(DIR_APP) && C_EXTRA_FLAGS=-fno-strict-aliasing
cd $(DIR_APP) && ./configure --prefix=/usr \
--sysconfdir=/etc \
--libexecdir=/usr/sbin \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-01-07 15:16 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=20140107151636.46E9F205A3@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