From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: kawa-3.1.1 released
Date: Sat, 18 Jan 2020 00:33:00 -0000 [thread overview]
Message-ID: <29b5b386-abc9-bc62-8d93-0d56aa808e10@bothner.com> (raw)
In-Reply-To: <CABgWrqoT2yHUWcDcJ3fSixH9QUcgOCDkUPLBZEcA6NajN2mo-w@mail.gmail.com>
On 1/17/20 4:12 PM, Duncan Mak wrote:
> I added the missing symlink on my local machine as a test, and running using Java 1.8 (which comes with JavaFX bundled), a window shows up when I run with --browse-manual=javafx.
I would not be terribly surprised if it is related to the incompatible readlink
command in the doc/browse-kanwa-manual script.
First thing to try is to run the script by hand.
The following works when I try it "by hand" in the Kawa build directory,
java kawa.repl doc/browse-kawa-manual
and the following works with the unzip'd release zip:
bin/kawa doc/browse-kawa-manual
as does running browse-kawa-manual as a shell script:
doc/browse-kawa-manual
So see if you can get any of those to work.
If you can get it working just treating browse-kawa-manual as a Scheme source file,
but running it as a shell script doesn't work, then it is likely
the shell portion of browse-kawa-manual has some Linux dependencies
(possibly the readlink) or bash-isms.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2020-01-18 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 21:19 Per Bothner
2020-01-16 21:22 ` ian
2020-01-17 3:29 ` Duncan Mak
2020-01-17 3:33 ` Duncan Mak
2020-01-17 6:34 ` Per Bothner
2020-01-17 18:31 ` Duncan Mak
[not found] ` <CABgWrqoT2yHUWcDcJ3fSixH9QUcgOCDkUPLBZEcA6NajN2mo-w@mail.gmail.com>
2020-01-18 0:33 ` Per Bothner [this message]
2020-02-28 21:22 ` Lassi Kortela
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=29b5b386-abc9-bc62-8d93-0d56aa808e10@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--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).