Hi,
Recently, Guix started building Emacs with native compilation.
I did 'guix pull' few days ago (I hadn't done it for a few months), and
it broke my Emacs.
The 'guix package -u emacs-next' finished building Emacs successfully.
However, when I start Emacs, the native compiler starts doing it's
jgart writes:
> ```
> λ guix import crate the-way
> ;;; Failed to autoload string->semver-range in (semver ranges):
> ;;; no code for module (semver ranges)
> Backtrace:
> In ice-9/boot-9.scm:
> 1752:10 9 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
>8 (apply-
---
mumi/web/view/html.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mumi/web/view/html.scm b/mumi/web/view/html.scm
index 552d435..171fbf9 100644
--- a/mumi/web/view/html.scm
+++ b/mumi/web/view/html.scm
@@ -167,7 +167,7 @@ simple query language. Here is a list of suppo
Hi Max,
On Wed, Oct 12, 2022 at 4:24 AM Max Brieiev wrote:
>
> Hi,
>
> Recently, Guix started building Emacs with native compilation.
>
> I did 'guix pull' few days ago (I hadn't done it for a few months), and
> it broke my Emacs.
>
> The 'guix package -u emacs-next' finished building Emacs succe
"Thompson, David" writes:
> Hi Max,
> I don't know of a fix, but Guix is tracking this issue here:
> https://issues.guix.gnu.org/issue/57878
I think the issue is related, but different. In the original issue, the
problem is the avalance of the compilation processes (AFAIU).
My problem is that I
On 11-10-2022 23:39, jgart wrote:
```
λ guix import crate the-way
;;; Failed to autoload string->semver-range in (semver ranges):
;;; no code for module (semver ranges)
Backtrace:
In ice-9/boot-9.scm:
1752:10 9 (with-exception-handler _ _ #:unwind? _ # _)
In unknown file:
8 (a
Hi,
On mer., 12 oct. 2022 at 14:44, Max Brieiev wrote:
> "Thompson, David" writes:
>> I wouldn't mind seeing native compilation disabled until upstream
>> improves the experience, but it's been decided that native compilation
>> is staying on. So, we're stuck on an old Guix until there's a
>> s
On Wed, 12 Oct 2022 14:24:26 +0200 Maxime Devos wrote:
That still throws:
guix shell guile-semver -- guix import crate the-way
;;; Failed to autoload string->semver-range in (semver ranges):
;;; no code for module (semver ranges)
Backtrace:
In ice-9/boot-9.scm:
1752:10 9 (with-exception-handl
Hi everyone,
I am trying to run "guix shell -C" inside another container created with
"guix shell -C". I figured out that I need to take care of three
aspects:
- Include the package "guix" in the outer container.
- --expose=/gnu/store such that guix-in-the-container can access the
store
-
On 2022-10-07, Efraim Flashner wrote:
> On Thu, Oct 06, 2022 at 04:50:22PM +0200, Ludovic Courtès wrote:
> Firstly, I'd like to mention that we, in general, have a minimum system
> requirement of 2GB of RAM, and IIRC there aren't a lot of armhf boards
> out there which have that much. We do have a
jgart writes:
> On Wed, 12 Oct 2022 14:24:26 +0200 Maxime Devos
> wrote:
>
> That still throws:
>
> guix shell guile-semver -- guix import crate the-way
> ;;; Failed to autoload string->semver-range in (semver ranges):
> ;;; no code for module (semver ranges)
> Backtrace:
> In ice-9/boot-9.sc
Hi Guixers,
What do you think if we were to implement "Guix Goals"?
The various language ecosystems have their own linters, formatters,
typecheckers, repls, test runners, etc.
What if Guix could manage them all?
`guix lint` in a python project would run mypy.
`guix lint` in a haskell project wo
12 matches
Mail list logo
