From: Per Bothner <per@bothner.com>
To: Peter <craven@gmx.net>, kawa@sourceware.org
Subject: Re: Android problems
Date: Thu, 18 May 2017 16:57:00 -0000 [thread overview]
Message-ID: <f2c540ba-9dc9-1f98-dfad-fd3041b3b77f@bothner.com> (raw)
In-Reply-To: <8760gy4ikw.fsf@nexoid.at>
On 05/18/2017 02:31 AM, Peter wrote:
> 1) Kawa seems to be compiled against 1.8, which uses
> java.lang.invoke.MethodHandle a lot, which Android does not seem to
> support.
Apparently Android O will support MethodHandles.
> Is there a simple way to compile a kawa.jar against 1.6, so I
> can use it for Android?
You need to build Kawa from source, using the configure flag
--with-android=/path/to/android.jar
These instructions should help; however, they are a bit out-of-date:
https://www.gnu.org/software/kawa/Building-for-Android.html
(Advice for updating the instructions would be very welcome.)
> 2) In the following code, I get a kawa segfault. It seems to be related
> to the anonymous inner class, if I factor that out, things work fine.
> ...
> Is this somehow my fault, or is this a bug in the compiler?
Could be both :-)
As a general rule, any segfault or NullPointerException in the compiler is a compiler bug.
(I don't count exceptions in for example user-written macro transformers - however,
the compiler should catch those and print a helpful error message.)
Sometimes a compiler bug is triggered by a bug in the application.
I was able to reproduce the NullPointerException, so I'll take a look later.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2017-05-18 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:31 Peter
2017-05-18 16:57 ` Per Bothner [this message]
2017-05-23 19:35 ` Per Bothner
2017-05-24 13:28 ` Peter
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=f2c540ba-9dc9-1f98-dfad-fd3041b3b77f@bothner.com \
--to=per@bothner.com \
--cc=craven@gmx.net \
--cc=kawa@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).