unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: emacs-devel@gnu.org
Subject: --with-ns "make all install" seems to be failing for incremental builds
Date: Sun, 07 Sep 2008 16:56:12 -0700	[thread overview]
Message-ID: <867i9n33z7.fsf@blue.stonehenge.com> (raw)


I pulled the latest CVS, and noticed a few .c file changes, so
as habit goes, I said "make all install", and got the following errors
during the installation phase:

mv: rename share/emacs/23.0.60/etc to ./etc: Directory not empty
mv: rename share/emacs/23.0.60/lisp to ./lisp: Directory not empty
mv: rename share/emacs/23.0.60/site-lisp to ./site-lisp: Directory not empty
mv: rename share/info to ./info: Directory not empty

These commands come from

      if test "${ns_appdir}" != ""; then \
        ( cd ${ns_appresdir} ; \
            if test -d share/emacs ; then mv -f share/emacs/*/* . ; fi ; \
                if test -d share/info ; then mv -f share/info . ; fi ; \
                    rm -fr share ) ; \
                      ( cd ${ns_appbindir}/libexec ; mv -f emacs/*/*/* . ; rm -fr emacs ) ; \
                        ( cd ${ns_appbindir}/bin ; rm -f emacs emacs-23* ; \
                            ln -sf ../libexec/* .) ; \
                            else true ; fi

in the top level Makefile, I think.

And sure enough, the .2 version of my DOC file wasn't moved into
place, so the resulting .app file doesn't have all of the required
data, and fails. "make bootstrap all install" works, however.

"rm -rf nextstep/Emacs.app" before install works, but suffers because
the entire installation is being reinstalled, something that was never
necessary with the old carbon Emacs.app.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion





                 reply	other threads:[~2008-09-07 23:56 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

  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=867i9n33z7.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=emacs-devel@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 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).