unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Klaus.Zeitler@alcatel-lucent.com
Cc: 16717@debbugs.gnu.org
Subject: bug#16717: Dumping: Can't update subspace record
Date: Thu, 13 Feb 2014 11:43:42 -0800	[thread overview]
Message-ID: <52FD206E.1090304@cs.ucla.edu> (raw)
In-Reply-To: <q5g1tz75b6y.fsf@destgd0h411156.de.alcatel-lucent.com>

[-- Attachment #1: Type: text/plain, Size: 504 bytes --]

On 02/13/2014 06:39 AM, Klaus Zeitler wrote:
> This looked like a Make problem to me and when I replaced the official 
> HP make with GNU make everything worked beautifully.

That's good, but it'd be better if the makefile worked with HP make as 
well.  That part of the makefile has evolved since 24.3, but I expect 
that part of the problem is that it's just too complicated, so I 
simplified it in the hopes of getting things to work.  Could you please 
try the attached patch with HP make?  Thanks.


[-- Attachment #2: hp1.diff --]
[-- Type: text/x-patch, Size: 1175 bytes --]

Only in emacs-24.3-hp/: ChangeLog.orig
Only in emacs-24.3-hp/: ChangeLog.rej
diff -pru emacs-24.3/Makefile.in emacs-24.3-hp/Makefile.in
--- emacs-24.3/Makefile.in	2013-03-04 19:42:28.000000000 -0800
+++ emacs-24.3-hp/Makefile.in	2014-02-13 11:41:21.935087020 -0800
@@ -556,17 +556,11 @@ install-arch-indep: lisp leim install-in
 	  ${write_subdir}
 	subdir=$(DESTDIR)${datadir}/emacs/site-lisp ; \
 	  ${write_subdir} || true
-	[ -z "${GZIP_PROG}" ] || \
-	  ( echo "Compressing *.el ..." ; \
-	    unset CDPATH; \
-	    thisdir=`/bin/pwd`; \
-	    for dir in $(DESTDIR)${lispdir} $(DESTDIR)${leimdir}; do \
-	      cd $${thisdir} ; \
-	      cd $${dir} || exit 1 ; \
-	      for f in `find . -name "*.elc" -print`; do \
-	        ${GZIP_PROG} -9n `echo $$f|sed 's/.elc$$/.el/'` ; \
-	      done ; \
-	    done )
+	[ -z "${GZIP_PROG}" ] || { \
+	  echo "Compressing *.el ..." && \
+	  find "$(DESTDIR)${lispdir}" "$(DESTDIR)${leimdir}" -name '*.elc' -exec sh -c \
+	    '${GZIP_PROG} -9n `expr "$$@" : "\\(.*\\)c"`' dummy '{}' ';'; \
+	}
 	-chmod -R a+r $(DESTDIR)${datadir}/emacs/${version} ${COPYDESTS}
 
 ## The above chmods are needed because "umask 022; tar ..." is not

  reply	other threads:[~2014-02-13 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <q5glhxj886p.fsf@destgd0h411156.de.alcatel-lucent.com>
2014-02-10 18:40 ` bug#16717: Dumping: Can't update subspace record Paul Eggert
2014-02-13 14:39   ` Klaus Zeitler
2014-02-13 19:43     ` Paul Eggert [this message]
2014-02-13 19:54       ` Glenn Morris
2014-02-13 19:56         ` Glenn Morris
2014-02-13 20:32           ` Eli Zaretskii
2014-02-14  8:31           ` Paul Eggert
2014-02-14  1:45       ` Stefan Monnier
2014-02-10 18:33         ` Paul Eggert
2014-02-14  7:51           ` Glenn Morris
2014-02-14 17:31             ` Stefan Monnier
2014-02-14 14:42       ` Klaus Zeitler
2014-02-14 15:49         ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52FD206E.1090304@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=16717@debbugs.gnu.org \
    --cc=Klaus.Zeitler@alcatel-lucent.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).