From: subsetpark <subsetpark@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
Date: Mon, 23 Aug 2021 03:49:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32640@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
New issue by subsetpark on void-packages repository
https://github.com/void-linux/void-packages/issues/32640
Description:
### System
* xuname: `Void 5.13.9_1 x86_64 GenuineIntel uptodate rrrmFFFF`
* package: `j-901.f_1`
### Expected behavior
`libj.so` is available on the default dynamic linker search path (ie, a system call like `dlopen("j")` should locate `libj.so`)
### Actual behavior
`libj.so` is present and functional at `/usr/lib64/j/j64/libj.so`, but not available in `/usr/lib64`.
### Steps to reproduce the behavior
Attempt to use dynamic linking to access the `libj.so` file provided in the J distribution.
Here's a minimal C program that demonstrates the difference (obviously, the `janet` package is installed on my system!):
```c
#include <dlfcn.h>
#include <stdio.h>
int main(int argc, char **argv) {
void *p = dlopen("libjanet.so", RTLD_NOW);
printf("Janet DLL pointer: %p\n", p);
void *q = dlopen("libj.so", RTLD_NOW);
printf("J DLL pointer: %p\n", q);
}
```
Here's the execution example on my system:
```
Desktop [] ⊕ gcc ex.c -ldl
Desktop [] ⊕ ./a.out
Janet DLL pointer: 0x5561857862c0
J DLL pointer: (nil)
```
next reply other threads:[~2021-08-23 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 1:49 subsetpark [this message]
2021-09-11 10:40 ` leahneukirchen
2021-09-12 16:05 ` subsetpark
2021-09-24 15:15 ` subsetpark
2022-06-02 2:15 ` github-actions
2022-06-17 2:13 ` [ISSUE] [CLOSED] " github-actions
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-32640@inbox.vuxu.org \
--to=subsetpark@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).