unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Modified remote file name syntax
Date: Tue, 14 Mar 2017 10:57:24 +0100	[thread overview]
Message-ID: <87y3w8qiyj.fsf@detlef> (raw)
In-Reply-To: <alpine.DEB.2.20.1703141828060.15096@calancha-pc> (Tino Calancha's message of "Tue, 14 Mar 2017 18:29:15 +0900 (JST)")

Tino Calancha <tino.calancha@gmail.com> writes:

Hi Tino,

> On Tue, 14 Mar 2017, Michael Albinus wrote:
>
>> Tino Calancha <tino.calancha@gmail.com> writes:
>>
>>> I see following error in *Async Shell Command*:
>>> (maybe someone suspect something)
>>>
>>> Warning: arch-dependent data dir
>>> '/usr/local/libexec/emacs/26.0.50/x86_64-pc-linux-gnu/': No such file
>>> or directory
>>> Warning: Lisp directory '/usr/local/share/emacs/26.0.50/lisp': No such
>>> file or directory
>>> Warning: Could not find simple.el or simple.elc
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>>
>>> The new Emacs instance shows the *scratch* buffer and the error:
>>> Cannot open load file: No such file or directory, mule-util
>>>
>>> Following also works fine.
>>> M-& which ~/bin/emacs -Q
>>>
>>> If i checkout the commit right before yours, that is
>>> f591765e2b6b9ec3fa3ff647c77a10c984f78133
>>> i don't reproduce the issue.
>>
>> Did you run "make bootstrap"? My commit changes autoloads; while working
>> on the patch I was urged several time to run a bootstrap in order to
>> bring Emacs in a proper state.
> Yes i did.  The problem still arise.

I have no further idea. However, messages like "Warning: Lisp directory
'/usr/local/share/emacs/26.0.50/lisp': No such file or directory" look
very suspicious.

If you run this constellation prior my patch (everything works fine),
could you check in the running Emacs where simple.el and other files are
located according to M-x locate-library ?

It seems also to me, that /usr/local/share/emacs/26.0.50/lisp should not
be in game. I suppose, that you haven't run "make install" yet;
everything at /usr/local/share might not contain the recent changes.

Best regards, Michael.



  reply	other threads:[~2017-03-14  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 17:20 Modified remote file name syntax Michael Albinus
2017-03-14  2:24 ` Tino Calancha
2017-03-14  8:48   ` Michael Albinus
2017-03-14  9:11     ` Tino Calancha
2017-03-14  9:20       ` Michael Albinus
2017-03-14  9:29         ` Tino Calancha
2017-03-14  9:57           ` Michael Albinus [this message]
2017-03-14 10:19             ` Tino Calancha
2017-03-14 13:30               ` Michael Albinus
2017-03-14 15:37                 ` Tino Calancha
2017-03-14 15:52                   ` Michael Albinus
2017-03-15  8:46                     ` Tino Calancha

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=87y3w8qiyj.fsf@detlef \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=tino.calancha@gmail.com \
    /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).