* [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
@ 2021-08-23 1:49 subsetpark
2021-09-11 10:40 ` leahneukirchen
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: subsetpark @ 2021-08-23 1:49 UTC (permalink / raw)
To: ml
[-- 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)
```
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
2021-08-23 1:49 [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path subsetpark
@ 2021-09-11 10:40 ` leahneukirchen
2021-09-12 16:05 ` subsetpark
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: leahneukirchen @ 2021-09-11 10:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/32640#issuecomment-917384413
Comment:
Problem is we have 3 libj.so, so which one should be used?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
2021-08-23 1:49 [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path subsetpark
2021-09-11 10:40 ` leahneukirchen
@ 2021-09-12 16:05 ` subsetpark
2021-09-24 15:15 ` subsetpark
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: subsetpark @ 2021-09-12 16:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
New comment by subsetpark on void-packages repository
https://github.com/void-linux/void-packages/issues/32640#issuecomment-917663705
Comment:
Presumably the same version that’s selected by the jconsole shim. The version selection is based on the system architecture (I think), so it seems safe to make that choice at install time?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
2021-08-23 1:49 [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path subsetpark
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
4 siblings, 0 replies; 6+ messages in thread
From: subsetpark @ 2021-09-24 15:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
New comment by subsetpark on void-packages repository
https://github.com/void-linux/void-packages/issues/32640#issuecomment-926708356
Comment:
Alternately, if we didn't want to make that decision for the user, we could provide a script that did the symlinking and post-install instructions which would point them to the script.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
2021-08-23 1:49 [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path subsetpark
` (2 preceding siblings ...)
2021-09-24 15:15 ` subsetpark
@ 2022-06-02 2:15 ` github-actions
2022-06-17 2:13 ` [ISSUE] [CLOSED] " github-actions
4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2022-06-02 2:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/32640#issuecomment-1144344973
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ISSUE] [CLOSED] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path
2021-08-23 1:49 [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path subsetpark
` (3 preceding siblings ...)
2022-06-02 2:15 ` github-actions
@ 2022-06-17 2:13 ` github-actions
4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2022-06-17 2:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
Closed 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)
```
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-06-17 2:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-23 1:49 [ISSUE] Package `j` provides `libj.so`, but it's not linked or copied into the default linker search path subsetpark
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
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).