From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 4CHlMb0oVGRcfgAASxT56A (envelope-from ) for ; Thu, 04 May 2023 23:50:53 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id qxHsMb0oVGRwJwEAauVa8A (envelope-from ) for ; Thu, 04 May 2023 23:50:53 +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 543F927CAB for ; Thu, 4 May 2023 23:50:53 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pugqA-0000Ri-Jx; Thu, 04 May 2023 17:50:18 -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 1pugq9-0000RI-Bg for guix-devel@gnu.org; Thu, 04 May 2023 17:50:17 -0400 Received: from mail-4322.protonmail.ch ([185.70.43.22]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pugq3-0002aA-U6 for guix-devel@gnu.org; Thu, 04 May 2023 17:50:17 -0400 Date: Thu, 04 May 2023 21:50:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1683237009; x=1683496209; bh=+BzYdrkQFutfHXDLOOPT3fcBT4BcZNCXZeqUqToDl0s=; h=Date:To:From:Cc:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=ZNKVLc/o8ZgEr389FQQw3eY8rTvnDpL6T30RTrbwcGx4Ot2OrmQ0s4fBV1wHvEVKb NbTkycnq2BxUkDvj13urE8kzojAmiKUsTqI3GZ2E57Q43AxOpRxI2DhoLmHLVzbcYr syXUCK2zajeAB25FJCJWPiHpOLK8eib7zGfgYcsA6lpsQke2sUry8aC+AiGjEEJf4/ s/CS+FMnf6+WVpZ/ZAozS7HJslu5PxtQIwfZ3FYnZSVOGlmhO8utAyWzF7KA+Jjm0j LCWTURknnSsfysO2nKMZ9CE0gn34ywFNWiS61wuWpqZvO1YxUlBBcD02cbjzKmHXvK lKkJttbRC008w== To: Katherine Cox-Buday From: John Kehayias Cc: Kaelyn , Christopher Rodriguez , 63267@debbugs.gnu.org, guix-devel@gnu.org Subject: Re: gcc-toolchain is missing libstdc++.so Message-ID: <87sfcbzrzy.fsf@protonmail.com> Feedback-ID: 7805494: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.22; envelope-from=john.kehayias@protonmail.com; helo=mail-4322.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_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=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=1683237053; a=rsa-sha256; cv=none; b=m20hTmqLzup/dkTUTxAtW/f2AxryjXXL53R+GVOfePCneqi5NRzhcibze9dQUeLS0q8LnS 6MQTuRT+gAeuUsiZgF/YLleHshO0XSZTeNABGAkjFAPtyXoVsmhcaSCgFmOm2io35wqo9U DTXX5KM9tlXujJn9SoOAnBX+AB5pdTQY87KZuMryRW6fz3gXcYi4sHFPdx4fVknEKXd7SL fp73rpLi8yFKAaE904ulqDnHzJ5rX72r8mKTAA5QPt5p226R4M4jzfHGfCWcUiSZPtEChf wu2yZCrcTF0wjPBoIFe7l1jEjbOk7HJ5DIvkOH8iZLpxu3qdU+UccLcsekydWw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b="ZNKVLc/o"; 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=1683237053; 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:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=+BzYdrkQFutfHXDLOOPT3fcBT4BcZNCXZeqUqToDl0s=; b=tbV0d5fMu2BgeZ1k2ndJ3uX0d5+PBF6TFFXaUXAMmNXlT1QsMR/44gB7WIhKSf9nopcnAI xJCapSk1G4t/5fOEY7xt/4LqgdQ5W1GgXqyD7w0Mjw3ryXTD3FISFnDNgwpX7As8X1eFuR lTvBdCIWo5qmMXInV3oDDxMrbzMKuFNTlOrX9tIVKIfmajDsKqTTz0mlrqkRgXGpmdBeP8 rmGZVHld9OSHF9c/amfHK5tCf/S73tm+8R4yIvoUUUPQ8FdeIwfFpuO3DBVZhL0AL2pr6I mNclbwH7+kkiDcIARkDJtFY35a2KN/MEldd9hIJiANSbjxxeTE9F1oTTybjOxw== X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b="ZNKVLc/o"; 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: -2.38 X-Spam-Score: -2.38 X-Migadu-Queue-Id: 543F927CAB X-TUID: v/3eFSzjyUYK Hi all, > 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 implement 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 passes the package and > optional output specifier to package->manifest-entry. But I digress a > little... Nice little hack Kaelyn, would you mind sharing somewhere? I wonder if this should be something we should have more easily anyway. On Thu, May 04, 2023 at 12:14 PM, Katherine Cox-Buday wrote: > On 5/4/23 11:33 AM, Kaelyn wrote: > >> Regarding solutions, I would prefer to have libstdc++ in it's own >> package or output rather than bundled into gcc-toolchain:out; it >> feels messy and against the grain of isolating programs in >> containers if I have to make the gcc and g++ compilers available in >> the container in order to run a program that needs libstdc++. > > +1. I recently ran into this as well and went looking for it. > > I think a good reason to give libstdc++ its own output is that this > question continually gets asked. That sounds reasonable to me as well. I would think the make-libstdc++ procedure would work for this, but as I detailed in my other message, I'm not sure why it seems to be missing symbols. We would have just what we need there and could just expose some public package versions through that or leave it similar to how it is and document (so it is more of an advanced or edge case scenario and not have more people going that way when what they really want is the actual gcc-toolchain package). John