Re: Tramp modified-p behaviour
Hi, Michael Albinus -
(Michael Kifer - I'm copying you because I had to add sh-script to the
list of ediff required packages.)
On Mon, Jan 21, 2013 at 3:13 AM, Michael Albinus <michael.albinus(a)gmx.de> wrote:
Vin Shelton <acs(a)alumni.princeton.edu> writes:
> The actual error is:
>
> byte-compile-report-error((file-error "Cannot open load file"
"executable"))
>
> which seems kinda weird. I'm investigating now, but in case someone
> has some ideas, I'd be happy for any pointers.
In (the new) tramp-compat.el, there is the following code snippet:
--8<---------------cut here---------------start------------->8---
(eval-and-compile
;; Some packages must be required for XEmacs, because we compile
;; with -no-autoloads.
(when (featurep 'xemacs)
(require 'cus-edit)
(require 'env)
(require 'executable)
(require 'outline)
(require 'passwd)
(require 'pp)
(require 'regexp-opt))
(require 'advice)
(require 'custom)
(require 'format-spec)
(require 'shell)
(require 'tramp-loaddefs)
...
--8<---------------cut here---------------end--------------->8---
I have added the "(when (featurep 'xemacs) ..." form, because there were
compilation errors otherwise in my local environment. But I'm open to
any enhancement.
OK. Thanks for the tip. I added sh-script to the requires lines of
ediff and pcl-cvs and I could compile those packages.
I can now build all the packages except tramp:
xemacs -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error
t load-always-display-messages t load-ignore-out-of-date-elc-files t
load-show-full-path-in-messages t)' -eval '(setq load-path (list
lisp-directory))' -l
/home/opt/build/xemacs-packages-2013-01-20/package-compile.el -- tramp
xemacs-base vc efs dired mail-lib gnus ediff sh-script edebug -- -f
batch-byte-compile lisp/tramp-gvfs.el
Loading /opt/xemacs/lib/xemacs-21.4.22/lisp/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/edebug/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/sh-script/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/ediff/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/gnus/lisp/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/mail-lib/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/dired/auto-autoloads...
Loading /home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/efs/auto-autoloads...
Loading /home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/vc/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/xemacs-base/auto-autoloads...
Loading
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/tramp/lisp/auto-autoloads...
Compiling
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/tramp/lisp/tramp-gvfs.el...
While compiling toplevel forms in file
/home/opt/build/xemacs-packages-2013-01-20/xemacs-packages/tramp/lisp/tramp-gvfs.el:
** reference to free variable dbus-get-unique-name
Loading customization dependencies...
Loading customization dependencies...done
!! File error (("Cannot open load file" "dbus"))
backtrace(nil t)
# bind (error-info)
byte-compile-report-error((file-error "Cannot open load file"
"dbus"))
# bind (error-info)
I could not find a dbus module anywhere in the XEmacs sources (not
21.4, 21.5 or packages). I'm pretty sure FSF emacs has dbus support -
is that something you've added to your XEmacs environment?
Please let me know what the right course of action is.
Regards,
Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta