From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: 47006@debbugs.gnu.org, 39480@debbugs.gnu.org,
maximedevos@telenet.be, efraim@flashner.co.il
Subject: [bug#39480] [bug#47006] [WIP PATCH v2 2/2] gnu: Add zig.
Date: Sat, 11 Sep 2021 22:01:31 +0200 [thread overview]
Message-ID: <d6c444c9a774780d5a3c63816925c34c2d809a65.camel@gmail.com> (raw)
In-Reply-To: <86wnnmnceg.fsf@mgsn.dev>
Hi Sarah,
Am Samstag, den 11.09.2021, 12:24 -0700 schrieb Sarah Morgensen:
> All,
>
> Apologies for the empty email earlier. That shows me for trying to
> send from mobile!
Curse those mobile applications with their small buttons amirite? :P
> Liliana,
>
> Liliana Prikler <liliana.prikler@gmail.com> writes:
>
> > I've added a patch to use explicit search paths rather than
> > whatever Zig used
> > before and tried fixing some (syntactic) errors with the tests, but
> > was
> > unsuccesful, as there appear to be failing tests in the suite
> > itself. Could
> > you have a look at the revised patch and check what flags you could
> > add to
> > the check phase to make it meaningful?
> >
> > Btw. I haven't checked whether my cosmetic changes to #:configure-
> > flags break
> > things or not. The end of the build phase puts a large amount of
> > stress onto
> > my system that I'd like to avoid at this hour.
>
> I'm still working through the tests, but I did find one issue that
> has cropped up either from your patch or from the 0.7.1 -> 0.8.1
> upgrade. This is from attempting to build tetris [0] (though I had
> to make a few syntax fixes, attached below, to build with 0.8.1):
W.r.t. the syntax fixes, that is probably an upstream issue or perhaps
an incompatibility introduced by zig itself. (Maybe already from 0.7.1
to 0.8.0?)
> --8<---------------cut here---------------start------------->8---
> Zig attempted to find the path to native system libc headers by
> executing this command:
> cc -E -Wp,-v -xc /dev/null
> error: unable to create compilation: UnableToSpawnCCompiler
> --8<---------------cut here---------------end--------------->8---
It appears zig tries to execute @command{cc}. Note, that this command
does not exist in Guix unless you install a symlink, so it will always
fail. We might want to investigate the source of this error to check
whether spawning a C compiler is indeed the right choice for what
they're claiming to try or whether our hard coding already takes care
of that.
> No combination of ZIG_LIB_DIRS and ZIG_INCLUDE_DIRS seems to fix
> it. Neither does --search-prefix.
>
> If I set CC=gcc, it works fine. But I think something changed such
> that it now has to fall back to this method of detection. I have no
> idea why.
Thanks for the info. I'll let you know once I find out more.
next prev parent reply other threads:[~2021-09-11 20:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1922b0a2ec237d217af54ed3ff7065e360d994c.camel@gmail.com>
2021-09-09 1:43 ` [bug#50449] [PATCH] Add zig Andrew Patterson
2021-09-09 13:32 ` [bug#47006] [PATCH 1/2] gnu: lld: Update to 12.0.0 Liliana Prikler
2021-09-09 13:32 ` [bug#47006] [PATCH 2/2] gnu: Add zig Liliana Prikler
2021-09-09 16:31 ` [bug#50449] " Sarah Morgensen
2021-09-09 18:18 ` Liliana Marie Prikler
2021-09-09 18:49 ` [bug#47006] [bug#50449] " Sarah Morgensen
2021-09-09 13:32 ` [bug#47006] [WIP PATCH v2 " Liliana Prikler
[not found] ` <0f6c5b692df8d06a0d7adddc9e5abf93894a366f.1631226695.git.liliana.prikler@gmail.com>
2021-09-11 9:52 ` iskarian
2021-09-11 19:24 ` Sarah Morgensen
2021-09-11 20:01 ` Liliana Marie Prikler [this message]
2021-09-12 4:42 ` Sarah Morgensen
2021-09-12 7:32 ` Liliana Marie Prikler
2021-09-12 7:39 ` Liliana Marie Prikler
2021-09-12 22:40 ` Sarah Morgensen
2021-09-14 16:17 ` Liliana Marie Prikler
2021-09-24 0:17 ` [bug#50449] " Sarah Morgensen
2021-09-09 13:32 ` [bug#50449] [PATCH v5] " Liliana Prikler
2021-10-31 8:06 ` [bug#47006] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6c444c9a774780d5a3c63816925c34c2d809a65.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=39480@debbugs.gnu.org \
--cc=47006@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=iskarian@mgsn.dev \
--cc=maximedevos@telenet.be \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.