From: Kaelyn via Guix-patches via <guix-patches@gnu.org>
To: "63393@debbugs.gnu.org" <63393@debbugs.gnu.org>
Subject: [bug#63393] [PATCH 0/2] Fix libstdc++.so and gcc-toolchain
Date: Tue, 09 May 2023 18:50:02 +0000 [thread overview]
Message-ID: <nJpIaVpIYRxrmpaCLRWX4_Wiv4hasCHFZH5A-HQQUb4wJ6xAUJ1K-yxWt1ApIvVPnvPtAeoYQrYoC945qyOvEibk0dseBeGPJUiZC2c9ibo=@protonmail.com> (raw)
In-Reply-To: <cover.1683650835.git.zimon.toutoune@gmail.com>
Hi,
I like the direction of this patch. However, if gcc-toolchain:lib is intended to provide the runtime libraries when the full compiler isn't needed, then I think the .a and .la files should be moved back to the main gcc-toolchain output (or a separate :static output) since they are for static linking and the .a files in particular can be sizeable.
Cheers,
Kaelyn
next prev parent reply other threads:[~2023-05-09 18:51 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 [this message]
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 ` [bug#63393] " Isaac van Bakel
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='nJpIaVpIYRxrmpaCLRWX4_Wiv4hasCHFZH5A-HQQUb4wJ6xAUJ1K-yxWt1ApIvVPnvPtAeoYQrYoC945qyOvEibk0dseBeGPJUiZC2c9ibo=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=63393@debbugs.gnu.org \
--cc=kaelyn.alexi@protonmail.com \
/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.