all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Rodriguez <yewscion@gmail.com>
To: bug-guix@gnu.org
Cc: guix-devel@gnu.org
Subject: gcc-toolchain is missing libstdc++.so
Date: Thu, 04 May 2023 10:46:06 -0400	[thread overview]
Message-ID: <pkmp4emt2km9nz.fsf@u6908d19b746052.ant.amazon.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]


Hello All,

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.

Is there another method for getting these needed shared libraries in a
guix system at this point? It's entirely possible I'm missing something.

I am CCing guix-devel@gnu.org per podiki[m]'s request.

Thanks!

-- 
Christopher Rodriguez
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2023-05-04 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 14:46 Christopher Rodriguez [this message]
2023-05-04 15:05 ` gcc-toolchain is missing libstdc++.so Christopher Rodriguez
2023-05-04 15:26   ` bug#63267: " John Kehayias via Bug reports for GNU Guix
2023-05-04 17:33     ` Kaelyn
2023-05-04 18:14       ` Katherine Cox-Buday
2023-05-04 15:23 ` bug#63267: Possible Solution Christopher Rodriguez
2023-05-04 17:34 ` bug#63267: gcc-toolchain is missing libstdc++.so John Kehayias via Bug reports for GNU Guix
2023-05-09 17:07   ` Simon Tournier
2024-04-17  5:21     ` John Kehayias via Bug reports for GNU Guix
2024-04-22  0:14       ` Simon Tournier
  -- strict thread matches above, loose matches on Subject: below --
2023-05-04 21:50 John Kehayias
2023-05-04 23:45 ` Kaelyn
2023-05-05 20:59   ` John Kehayias
2023-05-05 23:59     ` Kaelyn

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pkmp4emt2km9nz.fsf@u6908d19b746052.ant.amazon.com \
    --to=yewscion@gmail.com \
    --cc=bug-guix@gnu.org \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.