Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-java] rpath problem for llvm libs?
Date: Sat, 03 Dec 2011 17:15:21 +0100	[thread overview]
Message-ID: <jbdhuo$pe4$1@dough.gmane.org> (raw)
In-Reply-To: <CA+M6bXk94ukVFEva8Ab-RbvNe3pWuYkJWZkk-WS8CpKca83F4Q@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 03-12-11 16:42, Tom Rini schreef:
> On Fri, Dec 2, 2011 at 2:46 AM, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Hi,
>> 
>> I installed openjdk + openjdk-shark on my target and I get:
>> 
>> root@beaglebone:~# java dl failure on line 696Error: failed 
>> /usr/lib/jvm/java-6-openjdk/jre/lib/arm/shark/libjvm.so, because 
>> libLLVMARMCodeGen.so: cannot open shared object file: No such file or
>> directory
>> 
>> The 'fix' I used:
>> 
>> root@beaglebone:~# for i in /usr/lib/llvm2.9/libLLVM*.so ; do ln -sf
>> $i /usr/lib ; done
>> 
>> root@beaglebone:~# java Usage: java [-options] class [args...] (to
>> execute a class)
>> 
>> I came up with a number of workarounds, but I'm not sure which is
>> best:
>> 
>> 1) do the for ; ln thing in a postinst 2) have llvm install into
>> ${libdir} instead of ${libdir}${LLVM_RELEASE} 3) Use u-a for the libs 
>> 4) add rpaths 5) convince people java is evil and have them switch to
>> C
>> 
>> I have a preference for 5), but I suspect Henning would like a
>> different solution :)
> 
> Well, what's Fedora or Debian/Ubuntu look like here?

They seem to lack the shark jre, but the 'llvm' package looks like this:

root@dominion:/data/ssd# find /usr/lib | grep llvm | grep Printer | head -n2
/usr/lib/llvm/lib/libLLVMCellSPUAsmPrinter.a
/usr/lib/llvm/lib/libLLVMXCoreAsmPrinter.a

So if we were to follow that option 4) seems to be the way.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk7aSxcACgkQMkyGM64RGpGD4wCfQojBBu41NzAvjl9mT8vjPE+Y
lcUAnA6Bfne8yFGuw+5m9QSZbQ0fktht
=4DKv
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-12-03 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  9:46 [meta-java] rpath problem for llvm libs? Koen Kooi
2011-12-03 15:42 ` Tom Rini
2011-12-03 16:15   ` Koen Kooi [this message]
2011-12-03 16:34     ` Henning Heinold
2011-12-03 18:53       ` Koen Kooi
2011-12-04 11:14         ` Henning Heinold
2011-12-05 12:29           ` Koen Kooi

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='jbdhuo$pe4$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.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