From: Maxime Devos <maximedevos@telenet.be>
To: Ricardo Wurmus <rekado@elephly.net>, 53609@debbugs.gnu.org
Subject: [bug#53609] [PATCH v2 3/4] gnu: Add glibc-2.2.5.
Date: Sat, 05 Feb 2022 15:44:37 +0100 [thread overview]
Message-ID: <5f16fc59d50dc2be6deffbef2e01cdd18479971d.camel@telenet.be> (raw)
In-Reply-To: <20220205000823.2680-3-rekado@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Ricardo Wurmus schreef op za 05-02-2022 om 01:08 [+0100]:
> + ((#:configure-flags flags '())
> + #~(let ((out (assoc-ref %outputs "out"))
(assoc-ref %outputs "out") -> #$output
> + (headers (assoc-ref %build-inputs "kernel-headers")))
> + `("--enable-shared"
> + "--enable-static"
> + "--disable-sanity-checks"
> + "--build=i686-unknown-linux-gnu"
> + "--host=i686-unknown-linux-gnu"
Given that it's always compiled for i686-linux, even on x86_64, should
#:system "i686-linux" be set be added to 'arguments', such that glibc-
2.2.5 only needs to be compiled once? Likewise for the
'glibc-mesboot0' package (on core-updates).
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-05 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:35 [bug#53609] [PATCH] Add GHC 4 for the Haskell bootstrap Ricardo Wurmus
2022-01-28 17:48 ` [bug#53609] [PATCH 1/2] gnu: Add perl-5.14 Ricardo Wurmus
2022-01-28 17:48 ` [bug#53609] [PATCH 2/2] gnu: Add ghc-4 Ricardo Wurmus
2022-01-29 18:56 ` Ricardo Wurmus
2022-02-05 0:08 ` [bug#53609] [PATCH v2 1/4] gnu: Add perl-5.14 Ricardo Wurmus
2022-02-05 0:08 ` [bug#53609] [PATCH v2 2/4] gnu: Add gcc-2.95-wrapper Ricardo Wurmus
2022-02-05 0:08 ` [bug#53609] [PATCH v2 3/4] gnu: Add glibc-2.2.5 Ricardo Wurmus
2022-02-05 14:44 ` Maxime Devos [this message]
2022-02-05 0:08 ` [bug#53609] [PATCH v2 4/4] gnu: Add ghc-4 Ricardo Wurmus
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=5f16fc59d50dc2be6deffbef2e01cdd18479971d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53609@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).