From debbugs-submit-bounces@debbugs.gnu.org Fri Jul 05 18:47:07 2019 Received: (at 36346) by debbugs.gnu.org; 5 Jul 2019 22:47:08 +0000 Received: from localhost ([127.0.0.1]:53929 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hjWyx-0005vB-Ij for submit@debbugs.gnu.org; Fri, 05 Jul 2019 18:47:07 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:52679) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hjWyu-0005uf-5J for 36346@debbugs.gnu.org; Fri, 05 Jul 2019 18:47:05 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id B9A7521111; Fri, 5 Jul 2019 18:46:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 05 Jul 2019 18:46:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-type; s=fm3; bh=gdnlIDjcvi1a5LYc0yF892aeFs cVNzufzRrIVX/gQgM=; b=StC7xg6yM6bRz6YiUG+qxq3ORNFeiYd1z78Nnly2uu EnGj/T7uFfVaCav6m+hOLVKQkQqIQgpv0wcxxKcSkunyqVYp9GfFjWpOQRdcCave lCiuPwXzhZMJr8YJpvWVHzxEADQar8/86s7yQgHNF842XaMKmCUs0h1N6o8v2IaB g45VOizM8rlKTSjGNpRdnEUErGMCmgxUoYspnDj+NpJqjxLGPZkN4Qpj5xH4kUkp odefihHuBgInYIJQUJWCyPRhu3pe13Ir7CAwCSbvW0fAx6orkwBb+vhs8HkJz2Qr OL5EI0cRGAAYWkoo1E3yaUQet/7ZfA3SLdpAwsXDnjUw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=gdnlID jcvi1a5LYc0yF892aeFscVNzufzRrIVX/gQgM=; b=quDhUWN9qlykkfJghh7qLh Z6HUCnIE71Bez/8qvkvEDwf7TZUzXC4RLjH33urFlkPTrTHbwxhuuiRrTJHWZwpn 0vfrgd7XBDTwe03zP+3qy29g+xaTV7Vg7TjY/ZzT5FJtQ5dAkyzAFLGzBH7JMzz4 epujAgqyOA0K36NPhQMYc5fJcR9Gz9ZmUblQEa6lcnIX6w11WwEdH8Y0ovdB/fNs 2/VkcVEa/WnohBgM0TF0xRXfP/FwCbUQiZgILs/8N5n1DzKhNWXvyJFMNm8I/1DJ iYmlBN/dyqnRBN3KDeskjQCTgQmh1Joc2UACFbfm+8mMjPtcSqjl+r7FzV9UDXoQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfeehgddufecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufgjfhgffffkgggtsehgtderre dtredtnecuhfhrohhmpeforghrihhushcuuegrkhhkvgcuoehmsggrkhhkvgesfhgrshht mhgrihhlrdgtohhmqeenucfkphepiedvrdduiedrvddviedrudegtdenucfrrghrrghmpe hmrghilhhfrhhomhepmhgsrghkkhgvsehfrghsthhmrghilhdrtghomhenucevlhhushht vghrufhiiigvpedt X-ME-Proxy: Received: from localhost (140.226.16.62.customer.cdi.no [62.16.226.140]) by mail.messagingengine.com (Postfix) with ESMTPA id 0F4D080061; Fri, 5 Jul 2019 18:46:57 -0400 (EDT) From: Marius Bakke To: Carl Dong , 36346@debbugs.gnu.org Subject: Re: [bug#36346] [PATCH] gnu: Allow building toolchain with non-default libc. In-Reply-To: References: User-Agent: Notmuch/0.29.1 (https://notmuchmail.org) Emacs/26.2 (x86_64-pc-linux-gnu) Date: Sat, 06 Jul 2019 00:46:56 +0200 Message-ID: <87y31cqeu7.fsf@devup.no> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 36346 Cc: Carl Dong X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) --=-=-= Content-Type: text/plain Carl Dong writes: > From: Carl Dong > > * gnu/packages/base.scm (make-gcc-libc): Make public. > * gnu/packages/commencement.scm (make-gcc-toolchain): Add 'libc' > optional argument to specify using a non-default glibc package, also > make public. It would be easier to digest this patch if it came with an actual user of this change. Right now it complicates a very simple procedure for no apparent reason. Can you elaborate a bit on the use case? Guix excels at creating bespoke toolchains like these. It is easy to express this change as a new 'make-gcc-toolchain-with-custom-libc' procedure. So I'm not sure if it's worth changing 'make-gcc-toolchain', which serves a fairly specific use case. I would expect any reasonably complex toolchain to need further tweaks, and we cannot possibly support all such configuration inside 'make-gcc-toolchain'. Does that make sense? It does sound useful to make these procedures more generally accessible however. Perhaps 'make-gcc-toolchain' could be implemented in terms of a more generic 'make-toolchain' interface? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl0f02AACgkQoqBt8qM6 VPpLQggA1RBXndQ0HJCeUdSwO03moa691jd6USDQLUmZ4XRHEPKa8MF+q4C+7sef RegOezahQ2aIht5ze/Is13N4VFC+sK4jLtP3KjGab9HKwANKuNKMJy5GXAXDa7mJ aHsz+eME2LsZoJ0r6ZRmKEpqUpW7ypUNjEk/MeqErij6r9OB/u8z6OZs9gguE4rs yApllbnirW5HU6jYWJRBnJHu0A8ANWr/EJdsKLwyJHOFYZPfe+qpHoowDZqkVFkh K3cgLMQIkq0pMbjVVkL3yeucvmNqr8lAECO+jozBfFeKCaTODCrkEF+qW8SsVi0x aDlPRbXzRzvbf2QzehxLGMmq5YjNdQ== =rCq1 -----END PGP SIGNATURE----- --=-=-=--