From: Efraim Flashner <efraim@flashner.co.il>
To: "Motiejus Jakštys" <motiejus@jakstys.lt>
Cc: "Hilton Chain" <hako@ultrarare.space>, dan <i@dan.games>,
"Ekaitz Zarraga" <ekaitz@elenq.tech>,
74217@debbugs.gnu.org, "Noé Lopez" <noe@xn--no-cja.eu>
Subject: bug#74217: Bootstrapping Zig with no Binary Blobs
Date: Mon, 2 Dec 2024 09:40:01 +0200 [thread overview]
Message-ID: <Z01kUThyeFzXqZhr@3900XT> (raw)
In-Reply-To: <CA+jRjx2rAJMpkwO0y0aMc_X0wi=P+1uegYOQkq9zjLcgaBF=7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2260 bytes --]
On Sun, Dec 01, 2024 at 09:32:01PM +0200, Motiejus Jakštys wrote:
> On Fri, Nov 29, 2024 at 2:25 PM Hilton Chain <hako@ultrarare.space> wrote:
> >
> > On Fri, 29 Nov 2024 04:53:57 +0800,
> > Motiejus Jakštys wrote:
> > >
> > > [1 <text/plain; UTF-8 (quoted-printable)>]
> > > On Thu, Nov 28, 2024 at 5:20 PM Hilton Chain <hako@ultrarare.space> wrote:
> > > > Thanks! Then I'll keep abilists removed before we can reproduce one :)
> > >
> > > OK here it is for 0.11:
> > >
> > > 1. check out glibc-abi-tool 13576b1ea957882be7ff2c99f4cdc27454930219
> > > 2. rm -fr glibc/2.3{5,6,7,8}
> > > 3. apply the attached patch.
> > > 4. /path/to/zig-0.11/bin/zig run consolidate.zig
> > >
> > > ... which results in abilists
> > > 546e3c64b5c972b45c4c5c3e81fa1c73282db9377d57ae870d7abcb276f9605c.
> > >
> > > Motiejus
> > > [2 Backport-consolidate.zig-to-zig-0.11.0.patch <text/x-patch; US-ASCII (base64)>]
> > > From 23135302904467aa2e814500af6327408c46f52e Mon Sep 17 00:00:00 2001
> > > From: =?UTF-8?q?Motiejus=20Jak=C5=A1tys?= <motiejus@jakstys.lt>
> > > Date: Thu, 28 Nov 2024 22:52:13 +0200
> > > Subject: [PATCH] Backport consolidate.zig to zig 0.11.0
> > >
> > > ---
> > > consolidate.zig | 8 ++------
> > > 1 file changed, 2 insertions(+), 6 deletions(-)
> >
> > Thanks very much! I have added abilists for 0.9 and 0.10 as well.
>
> For the record, I have smoke-tested abilists on 0.9, 0.10, 0.11.0,
> 0.12.1 and 0.13. The test was as follows:
>
> 1. create a "hello world" C program that uses printf.
> 2. /gnu/.../zig-VERSION/bin/zig cc -target x86_64-linux-gnu.2.28
> hello.c -o hello
> 3. readelf -Ws hello
> 4. observe line (3) has line "printf@GLIBC_2.2.5".
> 5. run `hello` on non-guix and observe expected output.
Thank you for sharing that syntax for targeting specific glibc versions.
I'm continuing to try to build zig-0.10.0-610 on riscv64. I've had more
luck with powerpc64le but it's not the most convenient thing with
passing build targets between my computer and berlin.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-02 7:42 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 21:47 bug#74217: Bootstrapping Zig with no Binary Blobs Ekaitz Zarraga
2024-11-07 1:19 ` Hilton Chain via Bug reports for GNU Guix
2024-11-07 22:06 ` Noé Lopez via Bug reports for GNU Guix
2024-11-07 22:09 ` Ekaitz Zarraga
2024-11-11 11:42 ` Efraim Flashner
2024-11-11 11:56 ` Hilton Chain via Bug reports for GNU Guix
2024-11-11 12:02 ` Efraim Flashner
2024-11-08 17:43 ` bug#74217: [PATCH 0/2] Initial step on bootstrapping Zig Hilton Chain via Bug reports for GNU Guix
2024-11-08 17:44 ` bug#74217: [PATCH 1/2] gnu: Add zig-0.10.0-610-bootstrap Hilton Chain via Bug reports for GNU Guix
2024-11-08 17:44 ` bug#74217: [PATCH 2/2] gnu: Add zig-0.10.0-610 Hilton Chain via Bug reports for GNU Guix
2024-11-09 17:26 ` bug#74217: [PATCH 0/2] Initial step on bootstrapping Zig Hilton Chain via Bug reports for GNU Guix
2024-11-13 16:46 ` bug#74217: Bootstrapping Zig with no Binary Blobs Hilton Chain via Bug reports for GNU Guix
2024-11-13 18:10 ` Efraim Flashner
2024-11-13 23:40 ` Hilton Chain via Bug reports for GNU Guix
2024-11-14 1:05 ` Hilton Chain via Bug reports for GNU Guix
2024-11-14 6:05 ` Hilton Chain via Bug reports for GNU Guix
2024-11-14 9:22 ` Hilton Chain via Bug reports for GNU Guix
2024-11-14 9:41 ` Efraim Flashner
2024-11-15 3:29 ` Hilton Chain via Bug reports for GNU Guix
2024-11-15 14:30 ` Hilton Chain via Bug reports for GNU Guix
2024-11-16 6:54 ` Hilton Chain via Bug reports for GNU Guix
2024-11-16 7:13 ` Motiejus Jakštys
2024-11-16 7:18 ` Hilton Chain via Bug reports for GNU Guix
2024-11-16 17:03 ` Efraim Flashner
2024-11-16 18:59 ` Hilton Chain via Bug reports for GNU Guix
2024-11-17 1:39 ` Hilton Chain via Bug reports for GNU Guix
2024-11-17 7:16 ` Efraim Flashner
2024-11-17 14:51 ` Hilton Chain via Bug reports for GNU Guix
2024-11-18 12:00 ` Hilton Chain via Bug reports for GNU Guix
2024-11-19 13:13 ` Hilton Chain via Bug reports for GNU Guix
2024-11-21 13:06 ` Hilton Chain via Bug reports for GNU Guix
2024-11-28 11:08 ` Hilton Chain via Bug reports for GNU Guix
2024-11-28 12:41 ` Motiejus Jakštys
2024-11-28 15:20 ` Hilton Chain via Bug reports for GNU Guix
2024-11-28 20:12 ` Motiejus Jakštys
2024-11-28 20:14 ` Motiejus Jakštys
2024-11-28 20:53 ` Motiejus Jakštys
2024-11-29 12:25 ` Hilton Chain via Bug reports for GNU Guix
2024-11-29 14:51 ` Hilton Chain via Bug reports for GNU Guix
2024-12-01 19:32 ` Motiejus Jakštys
2024-12-02 7:40 ` Efraim Flashner [this message]
2024-12-02 5:11 ` Hilton Chain
2024-11-14 9:47 ` Motiejus Jakštys
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=Z01kUThyeFzXqZhr@3900XT \
--to=efraim@flashner.co.il \
--cc=74217@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
--cc=hako@ultrarare.space \
--cc=i@dan.games \
--cc=motiejus@jakstys.lt \
--cc=noe@xn--no-cja.eu \
/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).