From: Kay Zheng <l04m33@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: Kawa mailing list <kawa@sourceware.org>
Subject: Re: Incompatibility between the Android runtime and Kawa-generated field names
Date: Fri, 01 Sep 2017 04:15:00 -0000 [thread overview]
Message-ID: <CAJCc8Ow2fb-C1Wkx_X9E7FdL6Mm07Z38xb8Y_Z=+vv=S2LQwvQ@mail.gmail.com> (raw)
In-Reply-To: <19600c2a-f4fe-7241-2279-bb820854f20e@bothner.com>
Yes, I tested it and I think it worked. My app can launch cleanly. Thank you.
One little glitch though. I have built the Kawa source tree before,
and I had to remove patch-source-list manually after I applied the
fix, or Mangling.java wouldn't get pre-processed during the next
build. This had me confused for a while.
2017-08-31 23:39 GMT+08:00 Per Bothner <per@bothner.com>:
> On 08/30/2017 10:03 AM, Per Bothner wrote:
>>
>> On 08/30/2017 10:00 AM, Kay Zheng wrote:
>>>
>>> Does the old "mangling" code still exist somewhere? Could you point it
>>> out for me, to see if I can do something with it?
>>
>>
>> Looks like its still there, in Language.mangleName.
>>
>> However, I think it's best for me to do it. I've already started looking
>> into it, and the actual amount of work looks fairly easy. Easier than
>> explaining it ...
>
>
> Fix checked in. Please test it.
>
> The "controlling" change is the USE_SYMBOLIC field in
> gnu/expr/Mangling.java. This field's value depends on
> whether Android is configured.
>
> Some complications did turn up - though it was probably still
> easier than explaining what to do ...
>
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2017-09-01 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 16:10 Kay Zheng
2017-08-30 16:24 ` Per Bothner
2017-08-30 16:42 ` Kay Zheng
2017-08-30 17:00 ` Kay Zheng
2017-08-30 17:04 ` Per Bothner
2017-08-30 17:10 ` Kay Zheng
2017-08-31 15:39 ` Per Bothner
2017-09-01 4:15 ` Kay Zheng [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='CAJCc8Ow2fb-C1Wkx_X9E7FdL6Mm07Z38xb8Y_Z=+vv=S2LQwvQ@mail.gmail.com' \
--to=l04m33@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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).