From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 13a8724a20d83cda90cfaa9eebc2dba16e8ebbcd
Date: Wed, 03 Dec 2014 14:32:33 +0100 [thread overview]
Message-ID: <20141203133233.B16A221024@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1655 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 3.x development tree".
The branch, master has been updated
via 13a8724a20d83cda90cfaa9eebc2dba16e8ebbcd (commit)
from 771aef5d309a3539ceb8112c26a9fbafb91a01af (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 13a8724a20d83cda90cfaa9eebc2dba16e8ebbcd
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Dec 3 14:31:46 2014 +0100
cmake: Fix typo in pakfire macro
The typo caused that libraries where not correctly installed
on x86_64
-----------------------------------------------------------------------
Summary of changes:
cmake/cmake.macro | 2 +-
cmake/cmake.nm | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/cmake/cmake.macro b/cmake/cmake.macro
index 222a950..f37e5ef 100644
--- a/cmake/cmake.macro
+++ b/cmake/cmake.macro
@@ -3,7 +3,7 @@
#
__cmake = /usr/bin/cmake
-if "${lib}" == "lib64"
+if "%{lib}" == "lib64"
__cmake_lib_suffix = -DLIB_SUFFIX=64
end
diff --git a/cmake/cmake.nm b/cmake/cmake.nm
index c037f87..1227af7 100644
--- a/cmake/cmake.nm
+++ b/cmake/cmake.nm
@@ -5,7 +5,7 @@
name = cmake
version = 2.8.4
-release = 2
+release = 3
groups = Development/Tools
url = http://www.cmake.org
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2014-12-03 13:32 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=20141203133233.B16A221024@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