From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] nfs-utils on void: ldd failure on installed .so
Date: Wed, 01 Jan 2025 08:45:44 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53785@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
New issue by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/issues/53785
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.67_1 x86_64-musl GenuineIntel notuptodate rrrnDDFFFFFFFFFFFF
### Package(s) Affected
nfs-utils libnfsidmap
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
On glibc:
```
$ ldd /usr/lib/libnfsidmap/regex.so
linux-vdso.so.1 (0x00007ffc5abab000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007fdadaa22000)
/usr/lib64/ld-linux-x86-64.so.2 (0x00007fdadac3b000)
```
### Actual behaviour
On muslc:
```
$ ldd /usr/lib/libnfsidmap/regex.so
ldd (0x7f0f5f58f000)
libc.so => ldd (0x7f0f5f58f000)
Error relocating /usr/lib/libnfsidmap/regex.so: nfsidmap_config_get: symbol not found
Error relocating /usr/lib/libnfsidmap/regex.so: nfs4_get_default_domain: symbol not found
Error relocating /usr/lib/libnfsidmap/regex.so: idmap_verbosity: symbol not found
Error relocating /usr/lib/libnfsidmap/regex.so: idmap_log_func: symbol not found
```
### Steps to reproduce
This breaks my void-mklive workflows making dracut images of x86_64-musl with the nfs library installed. I remove the nfs library and it works again, so I've narrowed down my build problems to this library.
It seems consistently broken on musl, fixed on glibc. I've checked and it seems the libs are in fact compiled fresh on each build. Upgrading to 2.8.2 didn't help #53784
I've not yet looked at how it's actually being built to see what is broken there.
next reply other threads:[~2025-01-01 7:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 7:45 Vaelatern [this message]
2025-01-01 13:23 ` nfs-utils on musl: " slymattz
2025-01-03 1:08 ` Vaelatern
2025-01-04 5:28 ` classabbyamp
2025-01-04 5:41 ` classabbyamp
2025-01-04 6:23 ` classabbyamp
2025-01-04 12:29 ` jozzsi
2025-01-05 7:29 ` Vaelatern
2025-01-05 7:54 ` Vaelatern
2025-01-05 15:03 ` jozzsi
2025-01-05 15:04 ` jozzsi
2025-01-05 15:04 ` jozzsi
2025-01-05 15:04 ` jozzsi
2025-01-07 4:55 ` Vaelatern
2025-01-07 7:54 ` slymattz
2025-01-07 9:40 ` slymattz
2025-01-07 20:04 ` Vaelatern
2025-01-07 20:26 ` jozzsi
2025-01-07 20:29 ` Vaelatern
2025-01-07 22:42 ` jozzsi
2025-01-08 5:15 ` Vaelatern
2025-02-03 18:45 ` jozzsi
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53785@inbox.vuxu.org \
--to=vaelatern@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).