From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] duktape update, quick turn around
Date: Sun, 08 Oct 2017 09:32:34 -0400 [thread overview]
Message-ID: <20170908093234.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
As per the bug in duktape that Kevin found; I reported it to my friend Sami, and darned if he didn't fix it in a week; his fix on the master branch.
It's exciting to work with people like him; you know mozilla wouldn't have responded that quickly.
We took duktape snapshots in the past, but in order to stay current with bug fixes etc we should probably follow the master branch.
It took me a while to figure out how to do this, so let me save you some time.
git clone https://github.com/svaarala/duktape.git
make dist
cd dist
make -f Makefile.sharedlibrary
make -f Makefile.sharedlibrary install (as root)
make -f Makefile.cmdline
ln -s `pwd`/duk /usr/local/bin/duk (as root)
Not sure if you have to repeat the make dist step after each pull.
So Kevin, the bug you ran into in readiocaroline should be fixed.
The if /blah/ test passes in the shell and in jdb mode.
Karl Dahlke
next reply other threads:[~2017-10-08 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 13:32 Karl Dahlke [this message]
2017-10-09 1:56 ` Kevin Carhart
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=20170908093234.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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 NNTP newsgroup(s).