From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gcc: fix dynamic linker paths and default os library paths
Date: Sat, 19 Dec 2020 06:16:27 +0100 [thread overview]
Message-ID: <20201219051627.GcRiCQRHPmegJ5fd6zwyCj_tkKQox9GI-wQol8UPNk8@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: 933 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/27269#issuecomment-748421346
Comment:
Next steps that should follow:
1) change the `libdir` in `glibc` template to `/usr/lib64` for all 64-bit platforms and `/usr/lib32` for all 32-bit platforms, instead of `/usr/lib` for all other than `i686`
2) do the same as above in all of our build-styles, and in cross-toolchains
3) fix and rebuild major templates that are known to be affected by this: notably `mesa`, `pulseaudio`, `imlib2`; rebuild more as they are found
if we do all this, it should be possible to create "multilib" prefixes regardless of architecture and libc, e.g. by having `/usr/mymultilib` with a 32-bit Void of some architecture/libc (handle package installations in it with just `xbps-install` into the root) and then symlinking its dynamic linker to the right path + symlinking its `usr/lib` to `/usr/lib32`
next prev parent reply other threads:[~2020-12-19 5:16 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 [this message]
2020-12-20 23:00 ` [PR PATCH] [Merged]: " q66
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=20201219051627.GcRiCQRHPmegJ5fd6zwyCj_tkKQox9GI-wQol8UPNk8@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).