unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: pukkamustard <pukkamustard@posteo.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Zig on core-updates
Date: Fri, 17 Mar 2023 09:33:31 +0000	[thread overview]
Message-ID: <864jqjk6mo.fsf@posteo.net> (raw)
In-Reply-To: <ZBHLqRlLBrDm3Ghs@jurong>


Andreas Enge <andreas@enge.fr> writes:

> Just a one-package-failure-report: zig fails on core-updates, and I do not
> see why from the error message. If someone who knows the package could have
> a look, that would be great.

No solution, but maybe some pointers:

It seems like the installed `zig` binary segfaults.

This is the build failure message:

--8<---------------cut here---------------start------------->8---
starting phase `check'
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "/gnu/store/8pd12pn8n3ganc3y4776m44gjrfdvlvd-zig-0.10.1/bin/zig" arguments: ("build" "test" "-Dskip-stage1" "-Dskip-stage2-tests" "-Dskip-non-native") exit-status: #f term-signal: 11 stop-signal: #f> 
phase `check' failed after 0.0 seconds
command "/gnu/store/8pd12pn8n3ganc3y4776m44gjrfdvlvd-zig-0.10.1/bin/zig" "build" "test" "-Dskip-stage1" "-Dskip-stage2-tests" "-Dskip-non-native" failed with signal 11
--8<---------------cut here---------------end--------------->8---

When invoking the installed binary directly:

--8<---------------cut here---------------start------------->8---
$ /gnu/store/8pd12pn8n3ganc3y4776m44gjrfdvlvd-zig-0.10.1/bin/zig 
Segmentation fault
--8<---------------cut here---------------end--------------->8---

I'm afraid, I don't know anything about debugging segfaults. 

A hunch: This might have something to do with Zig not properly
supporting glibc 2.35: https://github.com/ziglang/zig/issues/12808

-pukkamustard


  reply	other threads:[~2023-03-17 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 13:44 Zig on core-updates Andreas Enge
2023-03-17  9:33 ` pukkamustard [this message]
2023-04-10 15:56   ` Andreas Enge
2023-04-11  5:11     ` Pjotr Prins
2023-04-17 13:01       ` Efraim Flashner

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=864jqjk6mo.fsf@posteo.net \
    --to=pukkamustard@posteo.net \
    --cc=andreas@enge.fr \
    --cc=guix-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/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).