From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74974 invoked by alias); 18 Dec 2015 20:00:48 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 74940 invoked by uid 89); 18 Dec 2015 20:00:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:js, ahh, Hx-languages-length:2156, nowadays X-HELO: mail-io0-f174.google.com Received: from mail-io0-f174.google.com (HELO mail-io0-f174.google.com) (209.85.223.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 18 Dec 2015 20:00:34 +0000 Received: by mail-io0-f174.google.com with SMTP id 186so102247712iow.0 for ; Fri, 18 Dec 2015 12:00:34 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.107.170.16 with SMTP id t16mr7696007ioe.65.1450468832667; Fri, 18 Dec 2015 12:00:32 -0800 (PST) Received: by 10.107.200.5 with HTTP; Fri, 18 Dec 2015 12:00:32 -0800 (PST) In-Reply-To: <56746287.70007@bothner.com> References: <56733C82.1050008@bothner.com> <56745B04.7040907@bothner.com> <56746287.70007@bothner.com> Date: Fri, 18 Dec 2015 20:00:00 -0000 Message-ID: Subject: Re: DomTerm - a new console for Kawa (and everyone else) From: Charlie Turner To: Per Bothner Cc: Kawa mailing list Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-q4/txt/msg00062.txt.bz2 I'm mostly sure that the ".jnilib" extension is deprecated (but still supported), and that nowadays, JNI dynamic libraries can use the same file extension as ordinary Mac OS X dynamic libraries (i.e. ".dylib"). Either way, yeah ".so" is not the right file extension on Macs. Ahh, interesting. Thanks for the background info. It may be easier to start with the server, as that avoids JavaFX issues. Perhaps try the --process option to avoid PTY issues: Yep; I've got a terminal in the browser! Thanks Per, I'll have a play. On 18 December 2015 at 19:46, Per Bothner wrote: > > > On 12/18/2015 11:28 AM, Charlie Turner wrote: >> >> I almost got this working on OSX. See my hacks in the attached patch >> file if you want to get where I got :-) [where the heck do you get >> err_sys from on our box??] > > >> In addition to that patch file, I also had to rename libpty.so to >> libpty.jnilib on OSX. I have no idea why. This is my first experience >> with Native Java :-) > > > I guess I should start using autoconf ... > Including --disable-javafx and --disable-pty configure options. > >> Sadly, I got lost after managing to get the DomTerm to run. make-pty >> completes, and then the DomTerm window pops up with a scroll-bar, but >> nothing else. I get this stack trace in the terminal window from which >> I launched make run-pty, > > > It may be easier to start with the server, as that avoids JavaFX issues. > Perhaps try the --process option to avoid PTY issues: > > make run-server SERVER_ARGS=--process > > Then you can open a web console windows in your browser to check for > error messages. > > You might enable the various verbosity options, including the one > in terminal.js: > this.verbosity = 2; // instead of 0 > > >> netscape.javascript.JSException: ReferenceError: Can't find variable: >> makeDomTerm > > > That suggests the JavaScript in repl.html didn't get executed, > or got executed in the wrong context, or something like that. > > I suggest try the server/browser combination first. > > > -- > --Per Bothner > per@bothner.com http://per.bothner.com/