From: Roel Janssen <roel@gnu.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: IcedTea is not linking correctly with libjvm.so
Date: Sun, 22 Oct 2017 17:55:34 +0200 [thread overview]
Message-ID: <87mv4jqirt.fsf@gnu.org> (raw)
In-Reply-To: <877evokzir.fsf@gmail.com>
Chris Marusich writes:
> Roel Janssen <roel@gnu.org> writes:
>
>> 1. Fix the recipe to make sure libjvm.so is found, and thus libnet.so is
>> linked correctly.
>>
>> 2. Copy or make a symlink of libjvm.so to the parent directory
>> (lib/amd64), where the other libraries are. Maybe then libnet.so can
>> find libjvm.so.
>
> (1) seems better than (2) if possible, but either of those solutions
> seem OK to me. But to be honest, I don't understand why this isn't a
> problem for icedtea outside of Guix. What are we doing that is
> different which prevents the library from being found?
Thanks for your reply!
I agree that (1) would be better than (2). The only problem I see with
this is that I don't see how to achieve (1), but I do see how to achieve
(2).
I tried running that Java app with CentOS's Java (openjdk 1.7.0), and it
has the exact same problem:
$ ldd /usr/lib/jvm/java-1.7.0-openjdk/jre/lib/amd64/libnet.so
linux-vdso.so.1 => (0x00007ffcc153d000)
libjvm.so => not found
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0b70d7e000)
libgconf-2.so.4 => /lib64/libgconf-2.so.4 (0x00007f0b70b4d000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f0b70816000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f0b705c5000)
libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007f0b70245000)
libjava.so => /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121-2.6.8.0.el7_3.x86_64/jre/lib/amd64/./libjava.so (0x00007f0b70019000)
libc.so.6 => /lib64/libc.so.6 (0x00007f0b6fc57000)
/lib64/ld-linux-x86-64.so.2 (0x00007f0b711ce000)
libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f0b6fa53000)
libdbus-glib-1.so.2 => /lib64/libdbus-glib-1.so.2 (0x00007f0b6f82b000)
libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f0b6f5e2000)
libffi.so.6 => /lib64/libffi.so.6 (0x00007f0b6f3da000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f0b6f1d6000)
libz.so.1 => /lib64/libz.so.1 (0x00007f0b6efbf000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f0b6ed98000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f0b6eb7e000)
libjvm.so => not found
libverify.so => /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.121-2.6.8.0.el7_3.x86_64/jre/lib/amd64/./libverify.so (0x00007f0b6e96e000)
librt.so.1 => /lib64/librt.so.1 (0x00007f0b6e765000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f0b6e504000)
libjvm.so => not found
>
> Solution (3) feels like more of a hack than (2), so I'm not sure about
> it. Maybe other have other opinions?
I agree that we should avoid solution (3).
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2017-10-22 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 7:05 IcedTea is not linking correctly with libjvm.so Roel Janssen
2017-10-21 9:16 ` Ludovic Courtès
2017-10-24 13:11 ` Roel Janssen
2017-10-21 20:38 ` Chris Marusich
2017-10-22 15:55 ` Roel Janssen [this message]
2017-10-22 20:37 ` Chris Marusich
2017-10-24 11:46 ` Roel Janssen
2017-10-24 13:17 ` Ricardo Wurmus
2017-10-30 10:22 ` Roel Janssen
2017-10-30 16:35 ` Ricardo Wurmus
2017-11-01 9:17 ` Roel Janssen
2017-11-01 16:03 ` Chris Marusich
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv4jqirt.fsf@gnu.org \
--to=roel@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).