From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Problem installing git version on debian sid
Date: Tue, 05 Dec 2017 06:58:56 -0800 [thread overview]
Message-ID: <87efo9uspb.fsf@prgmr.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1712041937320.6760@debian.pulsar.com> (Chuck Hallenbeck's message of "Mon, 4 Dec 2017 19:47:04 -0500 (EST)")
Hi Chuck,
First, you may not even need to build tidy from git. It may be as easy
as installing tidy5-dev or tidy-dev. I don't know what package name
they're using on Debian. If it is tidy-dev, make sure the major version
number is 5, so you don't get the ancient tidy. If you do need to
install tidy from git, you might be able to do something like:
CXX=g++ cmake
But I'm not sure. I don't know why cmake is checking for cpp as the C++
compiler. As Karl says, this is the C preprocessor. Maybe Debian's
cmake is buggy or misconfigured?
Anyway, if you can get tidy installed with one of those methods, you may
have better luck building edbrowse, which does not use any C++ these
days.
-- Chris
next prev parent reply other threads:[~2017-12-05 14:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:48 Chuck Hallenbeck
2017-12-04 18:19 ` Geoff McLane
2017-12-04 19:48 ` Chuck Hallenbeck
2017-12-04 20:23 ` Geoff McLane
2017-12-04 23:42 ` Kevin Carhart
2017-12-05 0:47 ` Chuck Hallenbeck
2017-12-05 14:58 ` Chris Brannon [this message]
2017-12-05 16:36 ` Chuck Hallenbeck
2017-12-05 16:54 ` Karl Dahlke
2017-12-05 17:26 ` Chuck Hallenbeck
2017-12-05 18:57 ` Geoff McLane
2017-12-05 20:03 ` Chuck Hallenbeck
2017-12-10 6:39 ` [Edbrowse-dev] what is dispatchEvent and is it needed? Kevin Carhart
2017-12-10 6:48 ` Karl Dahlke
2017-12-10 8:28 ` Kevin Carhart
2017-12-05 1:01 ` [Edbrowse-dev] Problem installing git version on debian sid Chuck Hallenbeck
2017-12-04 20:12 ` Chuck Hallenbeck
2017-12-04 20:36 ` Karl Dahlke
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=87efo9uspb.fsf@prgmr.com \
--to=chris@the-brannons.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).