From: Helmut Eller <eller.helmut@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The 'cross' directory
Date: Thu, 17 Aug 2023 20:52:33 +0200 [thread overview]
Message-ID: <m2il9dmrgu.fsf@gmail.com> (raw)
In-Reply-To: <834jky6rl7.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Aug 2023 10:44:20 +0300")
On Thu, Aug 17 2023, Eli Zaretskii wrote:
>> 8. Even with all the .elc files in place, make still wants to execute
>> bootstrap-emacs for things like
>>
>> GEN ../lisp/leim/quail/CCDOSPY.el
>> or
>> GEN ../../lisp/cedet/semantic/bovine/c-by.el
>> or
>> ELC ../lisp/loaddefs.elc
>>
>> I just waited and let it proceed, as I didn't know any shortcuts.
>
> Why is this a problem? If it runs on the host (which it should),
> that's okay. If it runs only after Emacs was dumped, that's indeed a
> problem, but again: in a release tarball all those *.elc files should
> already be present.
It's not a problem. It was just surprising to me; but I only have
superficial and probably incorrect understanding of the build process.
It might me a problem if switching frequently between build and host
machine is slow or impractical.
Helmut
next prev parent reply other threads:[~2023-08-17 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:09 The 'cross' directory Eli Zaretskii
2023-08-08 0:51 ` Po Lu
2023-08-09 3:47 ` Richard Stallman
2023-08-09 3:54 ` Po Lu
2023-08-13 1:43 ` Richard Stallman
2023-08-13 2:10 ` Po Lu
2023-08-13 2:14 ` Emanuel Berg
2023-08-13 5:39 ` Eli Zaretskii
2023-08-15 8:05 ` Helmut Eller
2023-08-15 11:44 ` Eli Zaretskii
2023-08-16 21:32 ` Helmut Eller
2023-08-17 7:44 ` Eli Zaretskii
2023-08-17 18:52 ` Helmut Eller [this message]
2023-08-15 9:45 ` Richard Stallman
2023-08-10 2:15 ` Richard Stallman
2023-08-10 16:37 ` Jose E. Marchesi
2023-08-10 17:01 ` [External] : " Drew Adams
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=m2il9dmrgu.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=eliz@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.