From: Stephen Hassard <steve@hassard.net>
To: Glenn Morris <rgm@gnu.org>
Cc: 17971@debbugs.gnu.org
Subject: bug#17971: 24.3.92; Patch to fix el compression on RHEL/CentOS 7
Date: Wed, 9 Jul 2014 06:56:27 -0700 [thread overview]
Message-ID: <CAAicSye3xQ2Dzrhqek17f6vmnJwH7dj+VD7GF28arq2Q+ZRx-g@mail.gmail.com> (raw)
In-Reply-To: <CAAicSyfwZgdiUi2RLD97Y1+i5kS1ZH1=n-YA45Vwg5ZHi0ME=Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]
Here's another update to the patch that more closely follows the behaviour
of the original Makefile and now works with a prefix that includes a space.
This is tested and works with gnu findutils 4.5.11.
On Tue, Jul 8, 2014 at 9:16 PM, Stephen Hassard <steve@hassard.net> wrote:
> For fun I built a copy of findutils-4.5.12 from alpha.gnu.org and found
> that it's suffering the same regression as CentOS's bundled find.
>
>
> On Tue, Jul 8, 2014 at 9:07 PM, Stephen Hassard <steve@hassard.net> wrote:
>
>> It's definitely a regression in CentOS7 vs 6.5. I've built a new 6.5 VM
>> and have confirmed that it compresses the .el files without problem.
>>
>> It seems to be a regression in the bundled findutils. I've pulled in the
>> find binary from CentOS 6.5 onto my CentOS 7 VM and the 'make install'
>> process completed without problems with the old find.
>>
>> The version are:
>>
>> CentOS 7:
>> findutils-4.5.11-3
>>
>> CentOS 6.5:
>> findutils-4.4.2-6
>>
>>
>>
>>
>> On Tue, Jul 8, 2014 at 6:10 PM, Glenn Morris <rgm@gnu.org> wrote:
>>
>>> Stephen Hassard wrote:
>>>
>>> > Here's the relevant output from the 'make install' on CentOS 7:
>>> >
>>> > ----
>>> > [ -z "/usr/bin/gzip" ] || { \
>>> > echo "Compressing *.el ..." && \
>>> > cd "/home/shassard/opt/emacs/share/emacs/24.3.92/lisp" && \
>>> > find . -name '*.elc' -exec /bin/sh -c \
>>> > '/usr/bin/gzip -9n `expr "$1" : "\\(.*\\)c"`' dummy '{}' ';'; \
>>> > }
>>> > Compressing *.el ...
>>> > find: './progmodes/make-mode.el': No such file or directory
>>>
>>> Do you know why this happens?
>>> What has changed since RHEL6, where it works fine?
>>>
>>> > I've attached a revised patch that adds the -9n flag to the gzip
>>> command
>>> > and switch back to -exec for find.
>>>
>>> This fails if DESTDIR contains spaces.
>>>
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 3158 bytes --]
[-- Attachment #2: 0001-Fix-regression-in-findutils-4.5.patch --]
[-- Type: text/x-diff, Size: 894 bytes --]
From e5abf3fc52980bc54984b8e228d41c7177c6e3bb Mon Sep 17 00:00:00 2001
From: Stephen Hassard <steve@hassard.net>
Date: Wed, 9 Jul 2014 06:54:46 -0700
Subject: [PATCH] Fix regression in findutils-4.5
---
Makefile.in | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Makefile.in b/Makefile.in
index 76a0304..97002e4 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -615,8 +615,9 @@ install-arch-indep: lisp install-info install-man ${INSTALL_ARCH_INDEP_EXTRA}
[ -z "${GZIP_PROG}" ] || { \
echo "Compressing *.el ..." && \
cd "$(DESTDIR)${lispdir}" && \
- find . -name '*.elc' -exec $(SHELL) -c \
- '${GZIP_PROG} -9n `expr "$$1" : "\\(.*\\)c"`' dummy '{}' ';'; \
+ find . -name '*.el' \
+ -exec ${SHELL} -c 'test -f {}c' \; \
+ -exec ${GZIP_PROG} -9n {} \; ; \
}
-chmod -R a+r "$(DESTDIR)${datadir}/emacs/${version}" ${COPYDESTS}
--
1.8.3.1
next prev parent reply other threads:[~2014-07-09 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 5:05 bug#17971: 24.3.92; Patch to fix el compression on RHEL/CentOS 7 Stephen Hassard
2014-07-08 6:04 ` Glenn Morris
2014-07-08 15:50 ` Stephen Hassard
2014-07-09 1:10 ` Glenn Morris
2014-07-09 4:07 ` Stephen Hassard
2014-07-09 4:16 ` Stephen Hassard
2014-07-09 13:56 ` Stephen Hassard [this message]
2014-07-09 16:34 ` Glenn Morris
2014-07-09 17:29 ` Stephen Hassard
2014-07-10 16:06 ` Glenn Morris
2014-07-10 17:14 ` Paul Eggert
2014-07-10 18:06 ` Glenn Morris
2014-07-10 18:49 ` Paul Eggert
2014-07-11 6:37 ` Paul Eggert
[not found] ` <CAAicSydhXppOY=uqe90yZNDMszY5VnJb632FZWH6NzJe+bH9Zg@mail.gmail.com>
2014-07-11 17:36 ` Paul Eggert
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=CAAicSye3xQ2Dzrhqek17f6vmnJwH7dj+VD7GF28arq2Q+ZRx-g@mail.gmail.com \
--to=steve@hassard.net \
--cc=17971@debbugs.gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.