From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-java] rpath problem for llvm libs?
Date: Mon, 05 Dec 2011 13:29:28 +0100 [thread overview]
Message-ID: <jbidf8$54c$1@dough.gmane.org> (raw)
In-Reply-To: <20111204111425.GA4871@rhein.zuhause.netz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 04-12-11 12:14, Henning Heinold schreef:
> On Sat, Dec 03, 2011 at 07:53:53PM +0100, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Op 03-12-11 17:34, Henning Heinold schreef:
>>> On Sat, Dec 03, 2011 at 05:15:21PM +0100, Koen Kooi wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE----- So if we were to follow that
>>>> option 4) seems to be the way.
>>>>
>>>> regards,
>>>>
>>>> Koen
>>>
>>> Hi,
>>>
>>> our original Idea was, that you can install diffrent llvm versions at
>>> the same time. We need to discuss if we have still the case or really
>>> only one version of llvm. If not we can use directly /usr/lib if not
>>> solution 4 with rpath is my favourit. Besides this llvm should go to
>>> core, but I wanted to wait for the 3.0 release and christmas holidays
>>> to do it.
>>
>> - From the llvm website: "December 1, 2011: LLVM 3.0 is now available
>> for download!"
>
> I know ;)
FWIW, even after 'fixing' the llvm problems with ln shark still shows some
problems:
root@beaglebone:~/java# javac -O Linpack.java
javac:
/OE/tentacle/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/llvm2.9-2.9-r0/llvm-2.9/include/llvm/Support/Casting.h:202:
typename llvm::cast_retty<To, From>::ret_type llvm::cast(const Y&) [with X =
llvm::ConstantInt, Y = llvm::Value*, typename llvm::cast_retty<To,
From>::ret_type = llvm::ConstantInt*]: Assertion `isa<X>(Val) && "cast<Ty>()
argument of incompatible type!"' failed.
Stack dump:
0. Running pass 'ARM Instruction Selection' on function
'@"com.sun.tools.javac.zip.ZipFileIndex$ZipDirectory::readEntry"'
Aborted
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk7cuSYACgkQMkyGM64RGpGM/wCcCekfcU2mGzHYPmY3pCk9ExXO
68kAnitsMmhDfADPCYA6NsTNRHP8Bujc
=qnMt
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-12-05 12:36 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
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 [this message]
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='jbidf8$54c$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.