* Why does the emacs executable depend on SOME_MACHINE_LISP?
@ 2009-10-02 7:03 Glenn Morris
2009-10-02 13:19 ` Stefan Monnier
0 siblings, 1 reply; 3+ messages in thread
From: Glenn Morris @ 2009-10-02 7:03 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
Hi,
I'm curious about the reason for this change:
2008-06-20 Stefan Monnier <monnier at iro.umontreal.ca>
* Makefile.in (emacs${EXEEXT}): Depend on the machine-specific files.
which amounts to adding ${SOME_MACHINE_LISP} to the dependencies of
emacs${EXEEXT}. AFAICS, it should just depend directly on $lisp and
DOC. The latter depends on SOME_MACHINE_LISP, so emacs depends on it
indirectly, but I don't see why you added the direct dependence.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Why does the emacs executable depend on SOME_MACHINE_LISP?
2009-10-02 7:03 Why does the emacs executable depend on SOME_MACHINE_LISP? Glenn Morris
@ 2009-10-02 13:19 ` Stefan Monnier
2009-10-02 16:24 ` Glenn Morris
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Monnier @ 2009-10-02 13:19 UTC (permalink / raw)
To: Glenn Morris; +Cc: emacs-devel
> I'm curious about the reason for this change:
> 2008-06-20 Stefan Monnier <monnier at iro.umontreal.ca>
> * Makefile.in (emacs${EXEEXT}): Depend on the machine-specific files.
> which amounts to adding ${SOME_MACHINE_LISP} to the dependencies of
> emacs${EXEEXT}. AFAICS, it should just depend directly on $lisp and
> DOC. The latter depends on SOME_MACHINE_LISP, so emacs depends on it
> indirectly, but I don't see why you added the direct dependence.
I can't remember what was the reason, but I suspect that
date: 2008-07-03 23:39:37 -0400; author: monnier; state: Exp; lines: +6 -1; commitid: kLQlf04BwIcb9r9t;
(${etc}DOC): Depend on ${lisp} rather than ${shortlisp}.
is a good explanation: when I applied that patch DOC did not depend on
${lisp}. So you're probably right that we can now undo this change to
emacs${EXEEXT}.
I'm curious, tho: why do you ask?
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Why does the emacs executable depend on SOME_MACHINE_LISP?
2009-10-02 13:19 ` Stefan Monnier
@ 2009-10-02 16:24 ` Glenn Morris
0 siblings, 0 replies; 3+ messages in thread
From: Glenn Morris @ 2009-10-02 16:24 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
Stefan Monnier wrote:
> date: 2008-07-03 23:39:37 -0400; author: monnier; state: Exp; lines: +6 -1; commitid: kLQlf04BwIcb9r9t;
> (${etc}DOC): Depend on ${lisp} rather than ${shortlisp}.
>
> is a good explanation: when I applied that patch DOC did not depend on
> ${lisp}. So you're probably right that we can now undo this change to
> emacs${EXEEXT}.
>
> I'm curious, tho: why do you ask?
No hidden agenda, just curious, as I said. I wondered why my GNU/Linux
emacs needed eg ns-win.elc pre-compiled (because of DOC), and how it
managed to work at all when eg common-win.elc was missing from $lisp
(because $SOME_MACHINE_LISP saved us). Then I wondered what was going
on with the dependencies in general. Thanks for explaining.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-10-02 16:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-02 7:03 Why does the emacs executable depend on SOME_MACHINE_LISP? Glenn Morris
2009-10-02 13:19 ` Stefan Monnier
2009-10-02 16:24 ` Glenn Morris
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).