From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Geoff McLane <ubuntu@geoffair.info>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Problem installing git version on debian sid
Date: Mon, 4 Dec 2017 14:48:12 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1712041417070.3184@debian.pulsar.com> (raw)
In-Reply-To: <ce2f706d-b331-551e-a576-4e1b0948b311@geoffair.info>
Hi Jeff,
On Mon, 4 Dec 2017, Geoff McLane wrote:
> Hi Chuck,
>
> Concerning HTML Tidy, not sure what you refer to when you say 'master.zip'?
> What README?
The README is in the edbrowse directory created by the git-clone . It
says to retrieve
https://github.com/htacg/tidy-html5/archive/master.zip
>
> We have just released 5.6.0, and that should be 5.6.0.zip, or if you want to
> build from the repo -
> $ git checkout master
> $ git pull
> and the version.txt file should contain 5.6.0, 2017.11.25, being the latest
> release...
Not sure how to get the 5.6.0 package from the above.
>
> But concerning your problem, not sure I really have the answer, but cmake
> should be able to find a working cxx/cpp compiler in your system...
>
> My cmake 3.2.2 in Ubuntu linux, 14.04 shows "Check ... /usr/bin/c++ --
> works"...
>
> Actually tidy does not require cxx/cpp - it is a pure C project - and you
> could add this to the CMakeLists.txt, like change the line -
> project (${LIB_NAME})
> to
> project (${LIB_NAME} C)
>
> And that will tell cmake to ONLY look for a C compiler... and might get tidy
> 5.6.0 built...
>
> But you will still need a cxx/cpp compiler for 'edbrowse', since it likewise
> has only cmake 'project (edbrowse)', in its CMakeLists.txt, which without the
> [LANGUAGE] option will likewise try to test both C and CXX by default,
> whether actually needed or not...
>
> The real question is why is your Debian sid failing on this most basic of
> cmake tests? A cxx/cpp compiler should be installed...
Well actually it is installed at /usr/bin/cpp, which is a symlink to
cpp-7 in the same directory. But that produced the error when
attempting to compile the test program. The error said the option -c
was not recognized by the preprocessor. .
>
> I hope others can address that...
>
> HTH, Geoff.
Thanks for your response ... I'm not sure I'm quite up to this.
>
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--
Here In Northeast Ohio, The Moon is Waning Gibbous (98% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Yvette's iPhone.
next prev parent reply other threads:[~2017-12-04 19:46 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 [this message]
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
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=alpine.DEB.2.21.1712041417070.3184@debian.pulsar.com \
--to=chuckhallenbeck@gmail.com \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=ubuntu@geoffair.info \
/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).