From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gcc: fix dynamic linker paths and default os library paths
Date: Mon, 21 Dec 2020 00:00:50 +0100 [thread overview]
Message-ID: <20201220230050.vzQMg7QNgJABGm-XA2ep-DvQNS9pNpFkCe1h6CAke_Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27269@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
There's a merged pull request on the void-packages repository
gcc: fix dynamic linker paths and default os library paths
https://github.com/void-linux/void-packages/pull/27269
Description:
Void used to mess with the dynamic linker paths, which is very wrong, so it's time to change that. The reason this was done was
because the lib32/64 symlinks were not available in unconfigured chroots (since base-files used to create them during configuration) and this has not been the case for a while, so there is nothing blocking this.
While at it, change the library paths to lib64 for 64-bit systems and lib32 for 32-bit systems. This merely changes the toolchain
and usually does not have much of an effect; dynamic libraries do not contain the paths (the search paths are controlled by
the dynamic linker). The lib32/64 symlinks are contained in base-files, so there is no harm in having this be consistent.
(no revbump: there is no harm in just preparing this before merging gcc10)
[ci skip]
@leahneukirchen
@void-linux/pkg-committers
prev parent reply other threads:[~2020-12-20 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 5:01 [PR PATCH] " q66
2020-12-19 5:15 ` q66
2020-12-19 5:16 ` q66
2020-12-20 23:00 ` q66 [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=20201220230050.vzQMg7QNgJABGm-XA2ep-DvQNS9pNpFkCe1h6CAke_Q@z \
--to=q66@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).