GNU bug report logs - #38613
Disabling bytecompilation on a list of files.

Previous Next

Package: guix;

Reported by: Brett Gilio <brettg <at> posteo.net>

Date: Sat, 14 Dec 2019 21:03:01 UTC

Severity: normal

Done: Brett Gilio <brettg <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Brett Gilio <brettg <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#38613: closed (Disabling bytecompilation on a list of files.)
Date: Fri, 27 Dec 2019 23:08:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Fri, 27 Dec 2019 17:07:05 -0600
with message-id <87r20ps6zq.fsf <at> gnu.org>
and subject line Re: bug#38613: Disabling bytecompilation on a list of files.
has caused the debbugs.gnu.org bug report #38613,
regarding Disabling bytecompilation on a list of files.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
38613: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38613
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Brett Gilio <brettg <at> posteo.net>
To: bug-guix <at> gnu.org
Subject: Disabling bytecompilation on a list of files.
Date: Sat, 14 Dec 2019 13:45:10 -0600
Hey all.

Just forwarding along an idea discussed between Leo Prikler, Tobias, and
I on IRC.

Recently I was trying to update our emacs-doom-themes package to a
fresher commit since it offers numerous new functionalities but there is
not a marked stable release of the package. In the process I found an
issue where some files have a bytecode compilation overflow issue during
the build phase. My sloppy work around as shown in
e9d8dee6c3d6e2ddff74841a3ab3a2ba2816bf27 was as such:

--8<---------------cut here---------------start------------->8---
;; XXX: There is a byte-code overflow issue in the latest
;; checkout which affects byte-compilation for several theme
;; files. The easiest way to work around this is to disable
;; byte-compilation until the issue is resolved.
;; <https://github.com/hlissner/emacs-doom-themes/issues/314>
(delete 'build)
--8<---------------cut here---------------end--------------->8---

Obviously just outright deleting the phase responsible for
bytecompilation is not the _best_ solution. So what Leo and I proposed
was adding a #:no-bytecomp which takes a list of REGEXP or files that
will be excluded from the in-place byte-compilation.

I wanted to float this idea by those of us who use the
emacs-build-system regularly.

Thanks!

-- 
Brett M. Gilio
Homepage -- https://scm.pw/
GNU Guix -- https://guix.gnu.org/


[Message part 3 (message/rfc822, inline)]
From: Brett Gilio <brettg <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Leo Prikler <leo.prikler <at> student.tugraz.at>,
 Brett Gilio <brettg <at> posteo.net>, 38613-done <at> debbugs.gnu.org
Subject: Re: bug#38613: Disabling bytecompilation on a list of files.
Date: Fri, 27 Dec 2019 17:07:05 -0600
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Brett Gilio <brettg <at> gnu.org> writes:
>
>
> [...]
>
>> Leo and Maxim,
>>
>> Do you think this feature addition to the emacs-build-system is good to
>> be pushed, then? I think it looks quite fine but I want to double check
>> before potentially doing something dumb.
>
> LGTM!
>
> Thank you!
>
> Maxim
>

Done! Thank you Leo and Maxim.

-- 
Brett M. Gilio
GNU Guix, Contributor | GNU Project, Webmaster
[DFC0 C7F7 9EE6 0CA7 AE55 5E19 6722 43C4 A03F 0EEE]
<brettg <at> gnu.org> <brettg <at> posteo.net>


This bug report was last modified 5 years and 150 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.