From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. defd8d008f9f28a3b91964b6fb7a4bfd11ace778
Date: Sun, 08 Sep 2013 20:49:58 +0200 [thread overview]
Message-ID: <20130908184958.A16BB20F93@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1591 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 defd8d008f9f28a3b91964b6fb7a4bfd11ace778 (commit)
from d94384214e360013d4b43c6a32125d18d9f275ad (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 defd8d008f9f28a3b91964b6fb7a4bfd11ace778
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Sep 8 20:48:34 2013 +0200
gcc: fix toolchain build with texinfo-5.x.
-----------------------------------------------------------------------
Summary of changes:
lfs/gcc | 3 +++
1 file changed, 3 insertions(+)
Difference in files:
diff --git a/lfs/gcc b/lfs/gcc
index 0bdecda..a9f124b 100644
--- a/lfs/gcc
+++ b/lfs/gcc
@@ -177,6 +177,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/gcc/gcc44-rh610785.patch
cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/gcc/gcc44-unwind-debug-hook.patch
+ # texinfo 5 syntax-fixes
+ cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/gcc-4.4.7-texinfo-5.patch
+
ifneq "$(ROOT)" ""
# Build gmp and mpfr internally in toolchain.
cd $(DIR_APP) && tar xfa $(DIR_DL)/gmp-$(GMP_VER).tar.bz2
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-09-08 18:49 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=20130908184958.A16BB20F93@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