unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: IcedTea is not linking correctly with libjvm.so
Date: Sat, 21 Oct 2017 13:38:04 -0700	[thread overview]
Message-ID: <877evokzir.fsf@gmail.com> (raw)
In-Reply-To: <87y3o56kve.fsf@gnu.org> (Roel Janssen's message of "Sat, 21 Oct 2017 09:05:57 +0200")

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

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?

Solution (3) feels like more of a hack than (2), so I'm not sure about
it.  Maybe other have other opinions?

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-10-21 20:38 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 [this message]
2017-10-22 15:55   ` Roel Janssen
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=877evokzir.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=roel@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).