From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Why `lisp' and `shortlisp'
Date: Thu, 03 Jul 2008 16:00:37 -0400 [thread overview]
Message-ID: <isprpuivq2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: jwvzloyri6g.fsf-monnier+emacs@gnu.org
Stefan Monnier wrote:
> Can someone explain to me why we have both `lisp' and `shortlisp' in
> src/Makefile.in? It appears to contain the same list of files, so
> I can't understand how it would make sense to sometimes refer to them
> via ../lisp and sometimes via ${lispsource}.
I wondered about this too. Perhaps:
$lisp specifies the full path for those who build in a different directory.
$shortlisp is needed for the comment above the rule for DOC:
/* We run make-docfile twice because the command line may get too long
on some systems. */
Perhaps $shortlisp is (more likely, was) needed to avoid overflowing
the command-line limit on "some" systems. Generating it from $lisp via
eg sed would have the same problem.
next prev parent reply other threads:[~2008-07-03 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 17:29 Why `lisp' and `shortlisp' Stefan Monnier
2008-07-03 20:00 ` Glenn Morris [this message]
2008-07-03 22:39 ` Stefan Monnier
2008-07-03 22:54 ` Glenn Morris
2008-07-04 1:13 ` Stefan Monnier
2008-07-04 1:43 ` Glenn Morris
2008-07-04 3:40 ` Stefan Monnier
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=isprpuivq2.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.