From: Ken Brown <kbrown@cornell.edu>
To: emacs-devel@gnu.org
Subject: Re: Building a release tarball generates trampoline files in eln-cache
Date: Sat, 16 Oct 2021 09:42:14 -0400 [thread overview]
Message-ID: <7d60cace-2a43-c96b-c043-858db8df388c@cornell.edu> (raw)
In-Reply-To: <83y26tgupl.fsf@gnu.org>
On 10/16/2021 5:55 AM, Eli Zaretskii wrote:
>> Date: Sat, 16 Oct 2021 12:30:02 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: kbrown@cornell.edu, emacs-devel@gnu.org
>>
>>>>> ced72b6e4c should fix this, please have a look if it works for you when
>>>>> you've the time.
>>>>
>>>> Thanks. Now those subr--trampoline*.eln files are no longer under
>>>> eln-cache, but they are directly under native-lisp/, not under its
>>>> 28.0.60-xxxx/ subdirectory. That doesn't sound right, does it?
>>>
>>> Correct, it does not. 2971a6890f hopefully should fix this.
>>
>> Will test shortly.
>
> Now the subr--trampoline*.eln files are in the right place, but this
> problem:
>
>> lisp/emacs-lisp/seq.elc: Error: Symbol’s function definition is void: gv-setter
>> lisp/term/xterm.elc: Error: Symbol’s function definition is void: t
>
> still exists. So something else is amiss here.
I'm seeing the errors too. It's possible that when I tested yesterday I only
checked the build, to make sure the trampoline files weren't being created in
eln-cache, but didn't actually run the built emacs.
Ken
next prev parent reply other threads:[~2021-10-16 13:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 8:19 Building a release tarball generates trampoline files in eln-cache Eli Zaretskii
2021-10-09 14:37 ` Ken Brown
2021-10-09 15:05 ` Eli Zaretskii
2021-10-09 15:39 ` Ken Brown
2021-10-09 17:33 ` Ken Brown
2021-10-09 17:51 ` Eli Zaretskii
2021-10-13 19:37 ` Andrea Corallo via Emacs development discussions.
2021-10-14 6:18 ` Eli Zaretskii
2021-10-15 7:35 ` Andrea Corallo via Emacs development discussions.
2021-10-15 18:08 ` Ken Brown
2021-10-16 8:34 ` Eli Zaretskii
2021-10-16 9:04 ` Andrea Corallo
2021-10-16 9:30 ` Eli Zaretskii
2021-10-16 9:55 ` Eli Zaretskii
2021-10-16 13:42 ` Ken Brown [this message]
2021-10-16 20:15 ` Andrea Corallo
2021-10-17 5:56 ` Eli Zaretskii
2021-10-18 20:46 ` Andrea Corallo
2021-10-27 16:32 ` Eli Zaretskii
2021-11-02 18:45 ` Eli Zaretskii
2021-11-02 19:22 ` Andrea Corallo
2021-11-02 19:44 ` Stefan Monnier
2021-11-02 19:47 ` Eli Zaretskii
2021-11-02 19:51 ` Andrea Corallo
2021-11-02 20:26 ` Stefan Monnier
2021-11-04 11:12 ` Eli Zaretskii
2021-11-05 15:39 ` Andrea Corallo
2021-11-05 15:49 ` Andrea Corallo
2021-11-08 15:07 ` Eli Zaretskii
2021-11-09 21:55 ` Andrea Corallo
2021-11-10 18:37 ` Eli Zaretskii
2021-11-11 15:08 ` Andrea Corallo
2021-11-11 16:50 ` Eli Zaretskii
2021-11-11 21:01 ` Andrea Corallo
2021-11-13 14:47 ` Eli Zaretskii
2021-11-13 20:33 ` Andrea Corallo
2021-11-15 17:34 ` Eli Zaretskii
2021-11-15 19:37 ` Andrea Corallo
2021-11-02 19:49 ` Andrea Corallo
2021-11-02 20:09 ` Andrea Corallo
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d60cace-2a43-c96b-c043-858db8df388c@cornell.edu \
--to=kbrown@cornell.edu \
--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 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).