unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hattuari <susudata@setidava.kushan.aa>
Subject: Builing from CVS doesn't refresh *.elc's
Date: Sun, 31 Oct 2004 10:49:31 -0500	[thread overview]
Message-ID: <iMadnXhJd_ONlxjcRVn-hg@speakeasy.net> (raw)

When I run make on the CVS image, it doesn't seem to update the lisp
bytecompiled files.  I've been doing `cvs update -dP && make extraclean
&& ./configure --prefix=$GNU_EMACS && make && make install'

Which works just fine, but the extraclean seems excessive.  maintainerclean
would do about the same thing, but that also seems excessive.  Should the
normal `make' refresh the elisp files? 

-- 
p->m == (*p).m == p[0].m

             reply	other threads:[~2004-10-31 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31 15:49 Hattuari [this message]
2004-10-31 16:01 ` Builing from CVS doesn't refresh *.elc's Johan Bockgård
2004-10-31 16:37   ` Hattuari

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=iMadnXhJd_ONlxjcRVn-hg@speakeasy.net \
    --to=susudata@setidava.kushan.aa \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).