From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: zlib-ng-2.0.2
Date: Fri, 26 Mar 2021 22:21:08 +0100 [thread overview]
Message-ID: <20210326212108.gKrYsX1-hTpK7Vabb3DXxEj7Mdymr24aIzbrgKC0IdU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29544@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/pull/29544#issuecomment-808514983
Comment:
> Please make the documentation a `README.voidlinux` file. And the current guidance only works on glibc.
>
> You don't want to preload the library, though. You want the dynamic linker to use it when something is linked against zlib, and for that it's more correct to use `ld_library_path` (idk what it looks like in glibc config).
Is there any alternative to `/etc/ld.so.preload` on `musl`? I'm on musl and as you said, it seems to be glibc-specific thing.
Adding `LD_LIBRARY_PATH=/usr/lib/zlib-ng:/usr/lib` to `/etc/environment` seems OK, what do you think?
next prev parent reply other threads:[~2021-03-26 21:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 17:28 [PR PATCH] New package: zlib-ng-2.0.1 Logarithmus
2021-03-17 17:45 ` [PR REVIEW] " ericonr
2021-03-17 17:45 ` ericonr
2021-03-17 17:45 ` ericonr
2021-03-17 17:45 ` ericonr
2021-03-17 18:12 ` Logarithmus
2021-03-17 18:26 ` Logarithmus
2021-03-17 18:27 ` Logarithmus
2021-03-17 18:30 ` [PR REVIEW] " Logarithmus
2021-03-17 18:31 ` [PR PATCH] [Updated] " Logarithmus
2021-03-17 18:32 ` [PR REVIEW] " Logarithmus
2021-03-17 18:32 ` Logarithmus
2021-03-17 18:39 ` ericonr
2021-03-17 18:40 ` ericonr
2021-03-17 18:41 ` ericonr
2021-03-17 19:29 ` [PR PATCH] [Updated] " Logarithmus
2021-03-26 20:38 ` [PR PATCH] [Updated] New package: zlib-ng-2.0.2 Logarithmus
2021-03-26 20:39 ` Logarithmus
2021-03-26 21:08 ` ericonr
2021-03-26 21:21 ` Logarithmus [this message]
2021-03-26 21:21 ` Logarithmus
2021-03-26 21:22 ` Logarithmus
2021-03-26 21:24 ` Logarithmus
2021-03-26 21:27 ` jnbr
2021-03-26 21:29 ` jnbr
2021-03-26 21:35 ` ericonr
2021-03-26 21:36 ` ericonr
2021-03-27 13:22 ` Logarithmus
2021-03-27 16:21 ` ericonr
2021-03-29 6:38 ` Logarithmus
2021-03-29 6:39 ` Logarithmus
2021-03-29 7:59 ` Logarithmus
2021-03-29 13:53 ` sgn
2021-03-29 13:54 ` [PR REVIEW] " sgn
2021-03-29 13:56 ` sgn
2021-03-29 13:56 ` sgn
2021-03-30 14:13 ` sgn
2021-03-30 14:14 ` sgn
2021-03-31 2:08 ` sgn
2021-06-07 13:56 ` ericonr
2021-06-07 13:56 ` [PR PATCH] [Closed]: " ericonr
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=20210326212108.gKrYsX1-hTpK7Vabb3DXxEj7Mdymr24aIzbrgKC0IdU@z \
--to=logarithmus@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).