From: Jason Rumney <jasonr@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Splitting and moving generic.el.
Date: Wed, 20 Apr 2005 13:31:37 +0100 [thread overview]
Message-ID: <42664BA9.3060002@gnu.org> (raw)
In-Reply-To: <87sm1lvect.fsf@xs4all.nl>
Lute Kamstra wrote:
>Jason Rumney <jasonr@gnu.org> writes:
>
>
>
>>Lute Kamstra wrote:
>>
>>
>>
>>>Doing (require 'generic-x) shouldn't load generic unless generic-x is
>>>loaded from source. Any idea why your lisp/generic-x.el isn't
>>>compiled?
>>>
>>>
>>generic-x.el is in the DONTCOMPILE list in the lisp makefile.
>>
>>
>
>DONTCOMPILE was bogus. Everything in it was compiled just the same.
>Just setting no-byte-compile prohibits compilation. Anyway, I removed
>DONTCOMPILE from the makefiles one week ago. I guess that generic-x
>didn't get compiled on your system because compilation failed due to
>the old lisp/generic.elc. If a lisp file fails to compile on
>GNU/Linux, bootstrap terminates with an error. Does that work
>differently on Windows or did you use "make -k bootstrap"?
>
>
I used "make recompile", which I mistakenly thought had worked, since it
didn't give any errors.
"make bootstrap" gives "Invalid escape sequence" on my machine, which is
another recent problem I haven't yet tracked down the cause of, but it
seems to be specific to the build environment on that machine.
next prev parent reply other threads:[~2005-04-20 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 9:05 Splitting and moving generic.el Jason Rumney
2005-04-20 10:50 ` Lute Kamstra
2005-04-20 11:36 ` Jason Rumney
2005-04-20 12:09 ` Lute Kamstra
2005-04-20 12:31 ` Jason Rumney [this message]
2005-04-20 13:27 ` Lute Kamstra
2005-04-20 17:11 ` Eli Zaretskii
2005-04-20 17:08 ` Eli Zaretskii
2005-04-20 20:58 ` Jason Rumney
2005-04-21 3:27 ` Eli Zaretskii
2005-04-20 17:05 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2005-03-30 9:03 Lute Kamstra
2005-04-05 18:58 ` Lute Kamstra
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=42664BA9.3060002@gnu.org \
--to=jasonr@gnu.org \
--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 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.