From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Getting kawa -w to work on OS X
Date: Wed, 18 Jan 2017 17:02:00 -0000 [thread overview]
Message-ID: <CABgWrqogUovRdNHwTj0t+XO2b9R-fzYOE=1FPrc+3GNcpbNKgg@mail.gmail.com> (raw)
In-Reply-To: <d8b96aed-0398-dc82-1f46-b5de8311304a@bothner.com>
Ah, yes, I did forget about the configure flags.
However, even using the configure line that you posted, I can't seem
to force the DomTerm backend to start.
I tried giving more flags to -w, and this is what I see:
duncan@furigana:~/git/Kawa (master)$ java kawa.repl -wjavafx
kawa: -wjavafx failed: java.lang.NoClassDefFoundError: org/domterm/Backend
if I just run java kawa.repl -w, I just get the Swing console,
regardless of the patch or not.
On Wed, Jan 18, 2017 at 1:50 AM, Per Bothner <per@bothner.com> wrote:
>
>
> On 01/17/2017 10:16 PM, Duncan Mak wrote:
>>
>> Hello Per,
>>
>> I just tried building kawa from source (using a checkout from the
>> gitlab repo) and "kawa -w" works if I build it locally.
>>
>> Running it from the official binary distribution fails
>>
>> (https://github.com/Homebrew/homebrew-core/pull/8301#issuecomment-273030690)
>> - this means there's something system-dependent that got baked into
>> the JAR file?
>
>
> My guess is the "system dependency" is DomTerm and/or JLine. If you build
> from source, if you don't specify the configure flags --with-domterm and/or
> --with-jline3
> then -w will be equivalent to -wswing - it won't try to use any of the
> DomTerm
> console variations. However, the binary distribution includes both,
> so -w will try to use Domterm (and jline) and fail.
>
> The old Swing console works, but it has some basic problems, specifically
> rather limited input editing.
>
> You can use the DomTerm and JLine from the binary distribution
> to build the source distribution:
> ./configure --with-domterm=/tmp/kawa-2.3
> --with-jline3=/tmp/kawa-2.3/lib/jline.jar
> assuming you unziped kawa-2.3.zip into /tmp
>
> You can also try the attached patch. You're supposed to see something like:
>
> $ bin/kawa -w
> java.lang.Error: setCurL:kawa.standard.Scheme@1a86f2f1
> th:Thread[main,5,main] p1:#|kawa:%N|# p2:#|%P.%N|#
> at gnu.expr.Language.setCurrentLanguage(Language.java:55)
> at gnu.expr.Language.setDefaults(Language.java:1206)
> at kawa.repl.getLanguage(repl.java:227)
> at kawa.repl.processArgs(repl.java:383)
> at kawa.repl.main(repl.java:820)
> Started web server on port 46315. Browse http://127.0.0.1:46315/
> java.lang.Error: DomTerm.run th:Thread[Thread-9,5,main] p1:#|kawa:%N|#
> p2:#|%P.%N|#
> at kawa.DomTermBackend.run(DomTermBackend.java:132)
> at java.lang.Thread.run(Thread.java:745)
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
--
Duncan.
next prev parent reply other threads:[~2017-01-18 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 6:17 Duncan Mak
2017-01-18 6:51 ` Per Bothner
2017-01-18 17:02 ` Duncan Mak [this message]
2017-01-18 20:50 ` Per Bothner
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='CABgWrqogUovRdNHwTj0t+XO2b9R-fzYOE=1FPrc+3GNcpbNKgg@mail.gmail.com' \
--to=duncanmak@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).