From: Phillip Lord <phillip.lord@russet.org.uk>
To: Ken Brown <kbrown@cornell.edu>
Cc: 23446@debbugs.gnu.org
Subject: bug#23446: 25.0.93; cursor-sensor-inhibit
Date: Wed, 04 May 2016 22:21:44 +0100 [thread overview]
Message-ID: <87pot134ev.fsf@russet.org.uk> (raw)
In-Reply-To: <6dec109f-8a2d-27ff-f9ae-f1db0b242059@cornell.edu> (Ken Brown's message of "Wed, 4 May 2016 14:14:00 -0400")
Ken Brown <kbrown@cornell.edu> writes:
> On 5/4/2016 12:37 PM, Phillip Lord wrote:
>> Ken Brown <kbrown@cornell.edu> writes:
>>
>>> On 5/4/2016 8:58 AM, Phillip Lord wrote:
>>>> I am getting the following error from a freshly bootstrapped emacs
>>>> launching with emacs -q
>>>>
>>>> Debugger entered--Lisp error: (void-variable cursor-sensor-inhibit)
>>>
>>>> I *think* it may be something amiss with loaddefs
>>>
>>> Try 'make -C lisp autoloads'.
>>
>>
>> I think you are on the right track.
>>
>> I often build out-of-source, where you can clean by just deleting
>> everything. But, this does not clean either loaddefs.el or the elc
>> files.
>
> 'make bootstrap' *does* remove loaddefs.el and the elc files, even in an
> out-of-source build.
>
> When you referred to a freshly bootstrapped emacs, did you mean that
> you ran 'make bootstrap'?
No, I mean build from a clean source tree. I rarely use make bootstrap
for this because you have to run configure first. Normally I clean with
git clean, or just delete the directory for out-of-source.
So, this looks like up a failure during updating rather than anything
else. Slightly surprised if it's only me, but there we have it.
Phil
next prev parent reply other threads:[~2016-05-04 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 12:58 bug#23446: 25.0.93; cursor-sensor-inhibit Phillip Lord
2016-05-04 13:45 ` Ken Brown
2016-05-04 16:37 ` Phillip Lord
2016-05-04 18:14 ` Ken Brown
2016-05-04 21:21 ` Phillip Lord [this message]
2016-05-04 22:00 ` Ken Brown
2016-05-04 22:50 ` Phillip Lord
2016-05-04 22:10 ` Glenn Morris
2016-05-04 22:51 ` Phillip Lord
2016-05-05 7:07 ` Andreas Schwab
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=87pot134ev.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=23446@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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.