From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Edbrowse Development <edbrowse-dev@lists.the-brannons.com>
Subject: [Edbrowse-dev] Edbrowse now installed on Debian Sid.
Date: Tue, 5 Dec 2017 18:05:27 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1712051803400.13460@debian.pulsar.com> (raw)
Hi folks,
Well, thanks Karl, fixing the #include's was simple as PI. One file,
two statements. I had to install libtidy-dev and duktape-dev, after
which edbrowse compiled and installed, using the tidy5 and duktape
packages supplied by Debian.
Sorry, Jeff, maybe another time.
Chuck
--
Here In Northeast Ohio, The Moon is Waning Gibbous (92% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Larry's iPhone.
reply other threads:[~2017-12-05 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.21.1712051803400.13460@debian.pulsar.com \
--to=chuckhallenbeck@gmail.com \
--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).