From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gcc: update to 13.2.0.
Date: Thu, 28 Dec 2023 04:21:10 +0100 [thread overview]
Message-ID: <20231228032110.zhYJqA1SIdJ4dwracUyWmpzXv5XWAyHvi-uRz834BEY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45500@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/45500#issuecomment-1870786276
Comment:
> It seems that we're bumping the revision for packages to force them to re-build with the new gcc/glibc version. However; how do we know which packages should be rebuilt and which shouldn't?
The libtool and mk-configure hard code gcc paths so they need to be rebuilt for a new gcc.
> After merge, will there still be packages that are built against the old glibc version but at runtime will link against the new installed glibc version?
Yes, that is by design.
next prev parent reply other threads:[~2023-12-28 3:21 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:09 [PR PATCH] " oreo639
2023-08-26 21:48 ` leahneukirchen
2023-09-10 22:36 ` [PR REVIEW] " tornaria
2023-09-10 22:39 ` tornaria
2023-09-11 0:51 ` [PR REVIEW] " oreo639
2023-09-11 12:57 ` leahneukirchen
2023-09-11 15:51 ` oreo639
2023-12-07 17:53 ` metaleap
2023-12-07 18:54 ` oreo639
2023-12-07 18:54 ` oreo639
2023-12-07 18:54 ` oreo639
2023-12-07 18:55 ` oreo639
2023-12-07 18:55 ` oreo639
2023-12-26 21:54 ` oreo639
2023-12-26 22:10 ` [PR PATCH] [Updated] " oreo639
2023-12-27 4:15 ` oreo639
2023-12-27 4:16 ` oreo639
2023-12-27 4:17 ` oreo639
2023-12-27 8:51 ` [PR REVIEW] " averyterrel
2023-12-27 9:05 ` [PR PATCH] [Updated] " oreo639
2023-12-27 9:05 ` [PR REVIEW] " oreo639
2023-12-27 10:56 ` oreo639
2023-12-28 2:51 ` simvux
2023-12-28 3:21 ` oreo639 [this message]
2023-12-28 3:21 ` oreo639
2023-12-28 3:21 ` oreo639
2023-12-28 3:22 ` oreo639
2023-12-28 3:23 ` oreo639
2023-12-28 3:30 ` [PR PATCH] [Updated] " oreo639
2023-12-28 3:32 ` oreo639
2023-12-29 1:27 ` [PR PATCH] [Updated] " oreo639
2024-01-10 16:12 ` dataCobra
2024-01-11 0:45 ` 22h49
2024-01-16 14:39 ` [PR PATCH] [Updated] " oreo639
2024-01-16 14:40 ` oreo639
2024-01-17 18:21 ` Calandracas606
2024-01-17 18:48 ` Calandracas606
2024-01-17 23:07 ` oreo639
2024-01-17 23:31 ` oreo639
2024-01-18 7:43 ` [PR PATCH] [Updated] " oreo639
2024-01-19 1:46 ` oreo639
2024-01-19 1:47 ` oreo639
2024-01-19 1:47 ` oreo639
2024-01-22 4:44 ` [PR PATCH] [Updated] " oreo639
2024-01-22 5:44 ` oreo639
2024-01-22 5:56 ` oreo639
2024-01-22 21:41 ` oreo639
2024-01-22 21:46 ` oreo639
2024-01-22 21:55 ` oreo639
2024-01-22 21:56 ` oreo639
2024-01-24 21:09 ` oreo639
2024-01-25 14:00 ` leahneukirchen
2024-01-27 2:30 ` [PR PATCH] [Updated] " oreo639
2024-01-27 9:27 ` oreo639
2024-01-27 22:34 ` oreo639
2024-01-28 1:40 ` oreo639
2024-01-28 5:27 ` oreo639
2024-01-28 23:43 ` [PR PATCH] [Closed]: " oreo639
2024-01-28 23:43 ` oreo639
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=20231228032110.zhYJqA1SIdJ4dwracUyWmpzXv5XWAyHvi-uRz834BEY@z \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).