From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 4171bf1c225abfbe3f81ac314d8b3b7679307734
Date: Mon, 30 Jan 2012 01:46:32 +0100 [thread overview]
Message-ID: <20120130004633.CA38D20146@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1584 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 4171bf1c225abfbe3f81ac314d8b3b7679307734 (commit)
from dc7883935dc270697a232e28834aac98cb89d95b (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 4171bf1c225abfbe3f81ac314d8b3b7679307734
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jan 30 01:46:18 2012 +0100
gcc: Fix syntax error in makefile.
-----------------------------------------------------------------------
Summary of changes:
gcc/gcc.nm | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/gcc/gcc.nm b/gcc/gcc.nm
index d84cdeb..845ad54 100644
--- a/gcc/gcc.nm
+++ b/gcc/gcc.nm
@@ -8,7 +8,7 @@ build_cloog_ppl = 1
name = gcc
version = 4.6.2
-release = 10
+release = 11
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = Development/Compilers
@@ -61,7 +61,8 @@ build
# If cloog support is enabled, we require the devel packages for build.
if "%{build_cloog_ppl}" == "1"
- requires += cloog-ppl-devel ppl-devel
+ requires += cloog-ppl-devel
+ requires += ppl-devel
end
# Build libquadmath (only on x86).
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-01-30 0:46 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=20120130004633.CA38D20146@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