From: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Build failure with latest CVS
Date: Tue, 18 Apr 2006 11:58:02 +0200 [thread overview]
Message-ID: <jevet7fbo5.fsf@sykes.suse.de> (raw)
With the latest CVS I'm getting this build failure:
Loading paths.el (source)...
Attempt to autoload tramp-completion-file-name-handler while preparing to dump
make[3]: *** [emacs] Error 255
This is caused by this change:
(tramp-completion-file-name-handler): Add autoload cookie for
adding to `file-name-handler-alist'.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2006-04-18 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 9:58 Andreas Schwab [this message]
2006-04-18 10:03 ` Build failure with latest CVS Juanma Barranquero
2006-04-20 5:08 ` Michael Albinus
2006-04-20 19:38 ` Richard Stallman
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=jevet7fbo5.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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).