From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zig: enable cross-compile support
Date: Sat, 03 Oct 2020 18:15:43 +0200 [thread overview]
Message-ID: <20201003161543.7gKlbGD0dND1W4cTmzdOs6owYZPIpVCbnb_tmv3qiWM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25004@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
New comment by Piraty on void-packages repository
https://github.com/void-linux/void-packages/pull/25004#issuecomment-703127332
Comment:
@ifreund said on irc (not sure how accurate that is though)
> ifreund: stage2 didn't ship with 0.6.0, real work on it started just after that release
> ifreund: 0.7.0 will ship with an incompleted stage2, the goal is to have a complete stage2 for 0.8.0
> ifreund: 0.7.0 should be released in the month after llvm 11 releases fyi
According to [zig-0.6.0 README](https://github.com/ziglang/zig/blob/0.6.0/README.md):
> Note: Stage 2 compiler is not complete. Beta users of Zig should use the Stage 1 compiler for now.
The way i see it, the current template builds stage1 by just calling `cmake ; make`, stage2 is not part of this template yet.
In the future, this template should be renamed to `zig-bootstrap` or similar and be used by the real stage2 zig (which could then maybe have it's own `build_style=zig`)
next prev parent reply other threads:[~2020-10-03 16:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 1:45 [PR PATCH] " jjsullivan5196
2020-09-21 1:49 ` [PR REVIEW] " ericonr
2020-09-21 1:55 ` jjsullivan5196
2020-09-21 1:56 ` jjsullivan5196
2020-09-21 2:29 ` ericonr
2020-09-21 9:38 ` [PR PATCH] [Updated] " jjsullivan5196
2020-09-21 9:39 ` [PR REVIEW] " jjsullivan5196
2020-09-21 9:57 ` jjsullivan5196
2020-09-21 10:14 ` [PR PATCH] [Updated] " jjsullivan5196
2020-09-21 12:43 ` ericonr
2020-09-21 14:28 ` ericonr
2020-09-21 14:29 ` ericonr
2020-09-21 19:07 ` ericonr
2020-09-21 19:16 ` ericonr
2020-09-21 19:21 ` [PR REVIEW] " ericonr
2020-09-21 19:32 ` ericonr
2020-09-21 19:35 ` ericonr
2020-09-21 20:31 ` jjsullivan5196
2020-09-21 20:34 ` [PR REVIEW] " jjsullivan5196
2020-09-21 20:35 ` jjsullivan5196
2020-09-21 20:43 ` jjsullivan5196
2020-09-21 22:16 ` ericonr
2020-09-21 22:40 ` [PR REVIEW] " ericonr
2020-09-21 22:52 ` ericonr
2020-09-21 23:10 ` jjsullivan5196
2020-09-22 2:01 ` [PR PATCH] [Updated] " jjsullivan5196
2020-09-22 2:04 ` jjsullivan5196
2020-09-22 2:05 ` [PR REVIEW] " jjsullivan5196
2020-09-22 2:07 ` ericonr
2020-09-22 2:23 ` jjsullivan5196
2020-09-28 21:24 ` pullmoll
2020-09-30 5:25 ` jjsullivan5196
2020-09-30 6:26 ` ericonr
2020-10-02 16:36 ` Piraty
2020-10-02 16:39 ` Piraty
2020-10-02 16:44 ` q66
2020-10-02 16:47 ` Piraty
2020-10-02 16:55 ` jjsullivan5196
2020-10-02 16:56 ` jjsullivan5196
2020-10-02 22:04 ` jjsullivan5196
2020-10-03 16:15 ` Piraty [this message]
2020-10-03 16:50 ` jjsullivan5196
2020-10-03 16:50 ` jjsullivan5196
2020-10-03 16:51 ` jjsullivan5196
2020-10-03 17:01 ` jjsullivan5196
2020-10-03 17:07 ` jjsullivan5196
2020-10-03 17:17 ` Piraty
2021-01-21 17:44 ` ericonr
2021-01-22 2:16 ` jjsullivan5196
2021-08-03 3:02 ` ericonr
2021-08-03 4:22 ` jjsullivan5196
2021-08-03 4:22 ` [PR PATCH] [Closed]: " jjsullivan5196
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=20201003161543.7gKlbGD0dND1W4cTmzdOs6owYZPIpVCbnb_tmv3qiWM@z \
--to=piraty@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).