From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 3da3ac98564bc97ba96bc2e10d5d6acb746a33de
Date: Thu, 14 Jan 2016 16:09:22 +0100 [thread overview]
Message-ID: <20160114150922.8C19C20F6E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1478 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, next has been updated
via 3da3ac98564bc97ba96bc2e10d5d6acb746a33de (commit)
from 8f2ac12a87a1308c5e9adc7e7adb7150d5a1b364 (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 3da3ac98564bc97ba96bc2e10d5d6acb746a33de
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jan 14 16:08:24 2016 +0100
gcc: remove gdb python files also in root build.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/gcc | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/gcc b/lfs/gcc
index 0c3a50f..00f64c6 100644
--- a/lfs/gcc
+++ b/lfs/gcc
@@ -286,6 +286,8 @@ endif
ifeq "$(ROOT)" ""
ln -svf ../usr/bin/cpp /lib
ln -svf gcc /usr/bin/cc
+ # remove gdb python files from libdir
+ rm -rf /usr/lib/*-gdb.py
else
ifeq "$(PASS)" "1"
ln -svf libgcc.a $$(/tools/bin/$(CROSSTARGET)-gcc -print-libgcc-file-name | sed 's/libgcc/&_eh/')
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-01-14 15:09 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=20160114150922.8C19C20F6E@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