all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, karol@mikronika.com.pl
Subject: Re: compiling cvs emacs
Date: Mon, 3 Jan 2005 12:42:24 -0600 (CST)	[thread overview]
Message-ID: <200501031842.j03IgOE11400@raven.dms.auburn.edu> (raw)
In-Reply-To: <003a01c4f1c2$67c3ef60$0200a8c0@sedrcw11488> (lennart.borgman.073@student.lu.se)

Lennart Borgman wrote:

   > what the problem is then.  I guess that bootstrapping updates
   > loaddefs.el automatically or not?  At least that would appear from the
   > messages that flash by.

   I never got time to learn this, but was there not some problems with the
   error messages just "flashing by"? And maybe it was those expressions in
   Makefile that updates loaddefs.el that was a problem on windows? (What OS
   was the OP using?)

I am not an expert on the Make files.  It might be that without some prior
form of `*clean' (I use make maintainer-clean) loaddefs actually does
not get updated.

What is definitely true is that the OP's loaddefs.el is out of date.

`coding-system-equal' no longer gets autoloaded.  The autoload cookie
got (deliberately or accidentally) removed when `coding-system-equal'
got moved from mule-util to mule on October 12, 2004.

Sincerely,

Luc.

  reply	other threads:[~2005-01-03 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-03 12:18 compiling cvs emacs Karol Szkudlarek
2005-01-03 14:23 ` Luc Teirlinck
2005-01-03 17:58 ` Stefan Monnier
2005-01-03 18:14   ` Luc Teirlinck
2005-01-03 18:30     ` Lennart Borgman
2005-01-03 18:42       ` Luc Teirlinck [this message]
2005-01-03 21:34         ` Karol Szkudlarek
2005-01-05  9:23   ` Karol Szkudlarek
2005-01-05 14:47     ` Luc Teirlinck
2005-01-05 15:05       ` Karol Szkudlarek

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=200501031842.j03IgOE11400@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=karol@mikronika.com.pl \
    --cc=monnier@iro.umontreal.ca \
    /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.