From: Rob Browning <rlb@defaultvalue.org>
Cc: emacs-devel@gnu.org
Subject: Re: Should lisp/Makefile.in custom-deps be using EMACS or emacs?
Date: Thu, 25 Jul 2002 14:45:41 -0500 [thread overview]
Message-ID: <878z3ziobe.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <200207251807.g6PI7S207666@aztec.santafe.edu> (Richard Stallman's message of "Thu, 25 Jul 2002 12:07:28 -0600 (MDT)")
Richard Stallman <rms@gnu.org> writes:
> In the case that fails, can you try running by hand under GDB the
> command that actually uses cus-dep.el and step through the code in
> init_lread which sets up load-path, to see why the installed Lisp
> directories end up in the value? That's the only way to
> figure this out. Treating it as a black box won't get anywhere.
OK, but I didn't realize ./src/emacs was doing anything wrong. In
lisp/Makefile, EMACS is set to ./src/emacs and EMACS is what's used to
run custom-deps. Isn't ./src/emacs the binary that's eventually
installed in bindir? If so, then isn't it *supposed* to be using the
installed Lisp directories (unless it's overridden by EMACSLOADPATH or
similar)?
If that's right, then I running gdb on emacs probably won't help, but
using $(emacs) instead of $(EMACS) would (or something similar). If
that's wrong, then part of the problem is that I'm misunderstanding
the semantics here.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
next prev parent reply other threads:[~2002-07-25 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 2:55 Should lisp/Makefile.in custom-deps be using EMACS or emacs? Rob Browning
2002-07-08 13:56 ` Eli Zaretskii
2002-07-08 14:23 ` Rob Browning
2002-07-08 16:06 ` Eli Zaretskii
2002-07-09 18:52 ` Richard Stallman
2002-07-23 17:10 ` Rob Browning
2002-07-25 18:07 ` Richard Stallman
2002-07-25 19:45 ` Rob Browning [this message]
2002-07-26 18:44 ` Richard Stallman
2002-07-26 19:57 ` Rob Browning
2002-07-27 20:28 ` Rob Browning
2002-07-29 1:12 ` Richard Stallman
2002-07-30 23:01 ` Rob Browning
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=878z3ziobe.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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.