all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Isaac van Bakel <isaac.vanbakel@inf.ethz.ch>
To: <63393@debbugs.gnu.org>
Subject: [bug#63393] [PATCH 0/2] Fix libstdc++.so and gcc-toolchain
Date: Thu, 26 Oct 2023 14:11:12 +0200	[thread overview]
Message-ID: <f2c1f573-4455-f3f2-3b55-191ae908f8b0@inf.ethz.ch> (raw)
In-Reply-To: <cover.1683650835.git.zimon.toutoune@gmail.com>

Hi,

Is there anything I can do to help (a version of) this patch get over 
the line?

I'm currently in a state when I want to use libgcc_s.so.1, which is only 
provided by gcc:lib, which doesn't set the library path properly. 
According to #25072, gcc-toolchain should support my use-case.

Thanks,

Isaac





      parent reply	other threads:[~2023-10-26 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 16:58 [bug#63393] [PATCH 0/2] Fix libstdc++.so and gcc-toolchain Simon Tournier
2023-05-09 17:04 ` [bug#63393] [PATCH 1/2] gnu: gcc-toolchain: Do not use gcc-final Simon Tournier
2023-05-09 17:04 ` [bug#63393] [PATCH 2/2] gnu: make-gcc-toolchain: Add 'lib' outputs Simon Tournier
2023-05-11 13:38   ` [bug#63393] [PATCH 0/2] Fix libstdc++.so and gcc-toolchain Ludovic Courtès
2023-05-09 18:50 ` Kaelyn via Guix-patches via
2023-07-16 18:33 ` John Kehayias via Guix-patches via
2024-01-16 22:16   ` Maxim Cournoyer
2024-01-24 17:08     ` Ludovic Courtès
2024-01-24 19:11       ` Maxim Cournoyer
2024-04-03 19:22   ` John Kehayias via Guix-patches via
2024-04-03 19:26     ` [bug#63393] [PATCH V2 1/2] gnu: gcc-toolchain: Do not use gcc-final John Kehayias via Guix-patches via
2024-04-03 19:27     ` [bug#63393] [PATCH V2 2/2] gnu: make-gcc-toolchain: Add gcc:lib John Kehayias via Guix-patches via
2024-04-10 21:21     ` [bug#63393] [PATCH 0/2] Fix libstdc++.so and gcc-toolchain Ludovic Courtès
2024-04-17  5:15       ` bug#63393: " John Kehayias via Guix-patches via
2023-10-26 12:11 ` Isaac van Bakel [this message]

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=f2c1f573-4455-f3f2-3b55-191ae908f8b0@inf.ethz.ch \
    --to=isaac.vanbakel@inf.ethz.ch \
    --cc=63393@debbugs.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.