From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: 65478@debbugs.gnu.org
Cc: Hilton Chain <hako@ultrarare.space>,
Andrew Tropin <andrew@trop.in>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#65478] [PATCH emacs-team] gnu: emacs-flim-lb: Explicitly compile files to bytecode.
Date: Thu, 24 Aug 2023 02:00:14 +0800 [thread overview]
Message-ID: <5629f5f427c30caa6d43f37ac28c3dd3f1501d01.1692813553.git.hako@ultrarare.space> (raw)
* gnu/packages/emacs-xyz.scm (emacs-flim-lb)[#:phases]: Replace 'build phase
to byte compile files explicitly.
---
gnu/packages/emacs-xyz.scm | 21 ++++++++++++++++++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 412ace373e..ecdfa235c7 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -37655,6 +37655,24 @@ (define-public emacs-flim-lb
(base32
"1wsnipyl3blldcl8ynmpj1mxfvl7kjmxd8gapl83vqd3r0l9cr6q"))))
(build-system emacs-build-system)
+ (arguments
+ (list
+ #:phases
+ #~(modify-phases %standard-phases
+ ;; FIXME: Following error occurs when native compiled:
+ ;; condition-case: Eager macro-expansion failure: (void-variable
+ ;; eof-block-branches).
+ (replace 'build
+ ;; Copied from emacs-build-system's build phase, with
+ ;; `emacs-compile-directory' replaced to
+ ;; `emacs-byte-compile-directory'.
+ (lambda* (#:key outputs inputs #:allow-other-keys)
+ (for-each delete-file (find-files "." "\\.el[cn]$"))
+ (let* ((emacs (search-input-file inputs "/bin/emacs"))
+ (out (assoc-ref outputs "out")))
+ (setenv "SHELL" "sh")
+ (parameterize ((%emacs emacs))
+ (emacs-byte-compile-directory (elpa-directory out)))))))))
(propagated-inputs (list emacs-apel-lb emacs-oauth2))
(home-page "https://www.emacswiki.org/emacs/WanderLust")
(synopsis
@@ -37694,9 +37712,6 @@ (define-public emacs-semi-epg
(define-public emacs-wanderlust
;; No release since Jan 15, 2010.
- ;; FIXME: Building with emacs-next-pgtk would yield a void variable related
- ;; macro-expansion failure at runtime, so don't rewrite emacs input of this
- ;; package.
(let ((version "2.15.9")
(revision "791")
(commit "8369b2d5170a174652294835dd9a18ed21a38cb2"))
base-commit: d58c6e25ff3d1e70fd9b0e07bdad1b335de8a979
--
2.41.0
next reply other threads:[~2023-08-23 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 18:00 Hilton Chain via Guix-patches via [this message]
2023-08-27 6:24 ` [bug#65478] [PATCH emacs-team] gnu: emacs-flim-lb: Explicitly compile files to bytecode Liliana Marie Prikler
2023-08-27 12:52 ` Hilton Chain via Guix-patches via
2023-08-27 15:13 ` Liliana Marie Prikler
2023-08-27 15:39 ` Hilton Chain via Guix-patches via
2023-08-27 15:49 ` Liliana Marie Prikler
2023-08-28 4:21 ` Hilton Chain via Guix-patches via
2023-08-28 18:28 ` Liliana Marie Prikler
2023-08-29 1:33 ` [bug#65478] [PATCH emacs-team v2] build: emacs-utils: Adjust `emacs-compile-directory' for Emacs 29 Hilton Chain via Guix-patches via
2023-08-30 19:40 ` Liliana Marie Prikler
2023-09-01 16:14 ` Hilton Chain via Guix-patches via
2023-09-01 16:15 ` [bug#65478] [PATCH emacs-team v3] " Hilton Chain via Guix-patches via
2023-09-01 19:37 ` Liliana Marie Prikler
2023-09-09 8:23 ` bug#65478: " Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5629f5f427c30caa6d43f37ac28c3dd3f1501d01.1692813553.git.hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=65478@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=hako@ultrarare.space \
--cc=liliana.prikler@gmail.com \
/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/guix.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).