public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, seventeen, updated. 8acdb5225dd15f9f09bc22973bf55fda244cd3bf
Date: Sun, 26 Oct 2014 20:52:03 +0100	[thread overview]
Message-ID: <20141026195203.D71E920718@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1665 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, seventeen has been updated
       via  8acdb5225dd15f9f09bc22973bf55fda244cd3bf (commit)
      from  57629914e8dd6559c163093312bd51adf677ddb7 (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 8acdb5225dd15f9f09bc22973bf55fda244cd3bf
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sun Oct 26 20:51:14 2014 +0100

    glibc: Fix build on x86
    
    Some files that are patched for ARM are not available
    on the x86 source tree. Hence the sed command should not
    be executed.

-----------------------------------------------------------------------

Summary of changes:
 lfs/glibc | 2 ++
 1 file changed, 2 insertions(+)

Difference in files:
diff --git a/lfs/glibc b/lfs/glibc
index 194f556..df3e392 100644
--- a/lfs/glibc
+++ b/lfs/glibc
@@ -284,8 +284,10 @@ endif
 	#   Makefile:235: *** mixed implicit and normal rules.  Stop.
 	cd $(DIR_APP) && sed -i 's/ot \$$/ot:\n\ttouch $$@\n$$/' manual/Makefile
 
+ifeq "$(MACHINE_TYPE)" "arm"
 	# http://sourceware.org/ml/libc-ports/2011-09/msg00018.html
 	cd $(DIR_APP) && sed -e "s/PIC/SHARED/g" -i ports/sysdeps/arm/{,eabi/}{set,__long}jmp.S
+endif
 
 ifeq "$(ROOT)" ""
 ifeq "$(MACHINE_TYPE)" "arm"


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-10-26 19:52 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=20141026195203.D71E920718@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