From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 4ABPAgPuU2TPGQEASxT56A (envelope-from ) for ; Thu, 04 May 2023 19:40:19 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id QFc+AgPuU2SSGgEA9RJhRA (envelope-from ) for ; Thu, 04 May 2023 19:40:19 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B62F146882 for ; Thu, 4 May 2023 19:40:18 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pucq9-0004Ce-T8; Thu, 04 May 2023 13:34:01 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pucq8-0003zq-1b for guix-devel@gnu.org; Thu, 04 May 2023 13:34:00 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pucq5-0003Bj-Nx for guix-devel@gnu.org; Thu, 04 May 2023 13:33:59 -0400 Date: Thu, 04 May 2023 17:33:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1683221626; x=1683480826; bh=HZaj/5EMk+b+KQI8uHsvpsZzY6lNNJ93B6kBoCa9q2E=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=afILIr8ho1Clcz1rMa+Fl0GZyPTRwkQZ3PAsHj+zOmOowtYqHZkYd/Xe6EEGnqZOr Us54VDkcTqIoZyMXwNLnBB3kpBAwC1ZaTm6haVix5AZNTaUDD4baRuI54npax4noY0 U2iPtvMe4N+SIfoHxxEZF4JNdYlcyIcuCv0V1yWseTUODLM/YDDnqBh78ik1cc4G6d 62niTRkR07cMMdH2MpuueQjkSDHOr11vxSNKmmhsQANzfqzEqR3wI0g9o+yPpa8Vmk pIM7LvZAdWxeFUqHUnMVf8tNty4NH46gA3pwhq/tuJ1xCwVbkmYiKN/dV/2QFX4Tdh fsK5UK4FWGCCQ== To: John Kehayias From: Kaelyn Cc: Christopher Rodriguez , 63267@debbugs.gnu.org, guix-devel@gnu.org Subject: Re: gcc-toolchain is missing libstdc++.so Message-ID: In-Reply-To: <874jos15kh.fsf@protonmail.com> References: <874jos15kh.fsf@protonmail.com> Feedback-ID: 34709329:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.70.43.16; envelope-from=kaelyn.alexi@protonmail.com; helo=mail-4316.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Seal: i=1; s=key1; d=yhetil.org; t=1683222018; a=rsa-sha256; cv=none; b=lDBj+Pvl82V/dtnZ3gVhQDtb+rPAOAFkKCLujKgxTjUgS7LRX+oiQ4IdScFBflmNxmDqPT EF9JFBAfNg7tqRI+x/vX1Gz6/lK+V3C+kUlMlNqYtIstzDQTXRk4Zd+YSpbDxN0lGaP8sn IT08o+mPo7gImMIZskEODxLZvL7o520G2ewmURnMMe3Stb9LXSltlZ5dmYwmReY9fNtFMX 9qOQx6LbRJQyvHBLe6msLf2Ad6z0swx6dwO0QCMS4DE7AJMecvOgqNnLUDqZT56P2OqXhB WrKYETgpmQni8cve0tCkl0R1FYMwNjVMO6xh5WOiEY52HD9XUq1faJA31JyZqg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=afILIr8h; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1683222018; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=HZaj/5EMk+b+KQI8uHsvpsZzY6lNNJ93B6kBoCa9q2E=; b=Ox4Z3/2IqTSLS0IUFiSuVYZuuzTvYocCm2l9uQtaY9zMNq4FIUrbJ9sVHrhPIx960CfKzr kNYebpahUTcEMUbc9rxNUmm6qSl22fyMoOwYjHQG0HzFVUcBVANCNnyAuuPRIfNLTWYqqz e6pjZRNOR5AzvNbM1zca0Yv4+P5iYkXwdZGqhqzdON5qCHMZIF7eoo9Je1uRbxbn3hzjSX cTmi9JcE/t5qOd/w81KfUDX/IKaauzw+L9NkGAdicglL+tWg6zvAPLg463ZejT8QTJCCXe XnziSkdmRiq2GL7KRNbN9itgINKiLddVlqh8daOuTfeJ0xtEi7fWsxtosI09uw== X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=afILIr8h; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -4.88 X-Spam-Score: -4.88 X-Migadu-Queue-Id: B62F146882 X-TUID: LTdT4MoQS4+c Hi, ------- Original Message ------- On Thursday, May 4th, 2023 at 3:26 PM, John Kehayias wrote: >=20 > Hi Christopher, >=20 > On Thu, May 04, 2023 at 11:05 AM, Christopher Rodriguez wrote: >=20 > > Sorry for the spam; Resending this without the bugs address, but with > > the issue's address. > >=20 > > Christopher Rodriguez yewscion@gmail.com writes: > >=20 > > > Hello All, > > >=20 > > > I noticed today that libstdc++.so.1 (and some others), which used to = be > > > part of gcc:lib, are not included in any of the outputs of the > > > superceding `gcc-toolchain` package. > > >=20 > > > Is there another method for getting these needed shared libraries in = a > > > guix system at this point? It's entirely possible I'm missing somethi= ng. > > >=20 > > > I am CCing guix-devel@gnu.org per podiki[m]'s request. > > >=20 > > > Thanks! >=20 >=20 > Thanks for opening this and cc'ing; this has come up with some > frequency on IRC, especially recently. In discussing there today, the > current reasoning is that usually one will just call g++ which knows > how to find libstdc++. So, gcc-toolchain does not include gcc:lib as > part of what it makes available. >=20 > I think what we (and when this comes up, others) are getting at are > some edge cases or different use cases where one wants to directly get > at libstdc++. Previously it was more direct to use gcc:lib; of course > one still can in code and/or cli with the proper call. For example, > guix build -e "(@@ (gnu packages gcc) gcc)" will download/build/show > the lib output of the (hidden) gcc package. Though I'm not sure how to > select just the lib output here. >=20 > My use case currently is in the FHS container where a binary wants to > find some libraries directly. Previously one would include the gcc:lib > package output in the guix shell call. Now some of those libraries can > be found elsewhere, like libgccjit, but libstdc++ seems to be the > trickier one. Open to other suggestions/workarounds, or thoughts on if > it is worthwhile to include gcc:lib in the gcc-toolchain package (or > make a gcc-toolchain:lib output?). I have similar use cases of FHS containers to run binaries (primarily games= ). I recently ran into the issue of gcc:lib going away and no output from a= visible package providing libstdc++. My current workaround was to implemen= t a replacement for specifications->manifest that could handle packages and= '(package "output") pairs in addition to strings, so that I could include = `(,(@@ (gnu packages gcc) gcc) "lib") in place of "gcc:lib". Internally it = resolves package strings to packages with specification->package, then pass= es the package and optional output specifier to package->manifest-entry. Bu= t I digress a little... Regarding solutions, I would prefer to have libstdc++ in it's own package o= r output rather than bundled into gcc-toolchain:out; it feels messy and aga= inst the grain of isolating programs in containers if I have to make the gc= c and g++ compilers available in the container in order to run a program th= at needs libstdc++. Cheers, Kaelyn