edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] tidySetOptBool vs tidySetOptInt on debian
Date: Sat, 7 Dec 2019 19:49:28 +0000	[thread overview]
Message-ID: <20191207194928.GD194728@toaster> (raw)
In-Reply-To: <20191207193433.GA15586@nautica>

On Sat, Dec 07, 2019 at 08:34:33PM +0100, Dominique Martinet wrote:
> Alfonso S. Siciliano wrote on Sat, Dec 07, 2019:
> > 2 day ago I had the same problem with FreeBSD, the problem was the version of
> > tidy-html5, the discussion and fix is:
> > 
> > https://github.com/CMB/edbrowse/issues/53
> 
> Ah, yeah, if edbrowse compiled with headers from tidy-html5 but linked
> against tidy 0.99 it can't work...
> 
> Adam, can you confirm it's the same thing? What does `dpkg -l | grep tidy` list?

It's the same issue but that analysis in the link doesn't match the error in
the assertion (also in the linked issue) unless I'm missing something.

Anyway:
dpkg -l | grep tidy
ii libtidy-dev:amd64 2:5.6.0-10 amd64 HTML/XML syntax checker and
reformatter - development
ii libtidy5deb1:amd64 2:5.6.0-10 amd64 HTML/XML syntax checker and
reformatter - shared library

So no weird linkage on my side.  I wonder if tidySetOptInt also fixes the
FreeBSD port as it's fixed my version (and yes I've compiled and tested this
on Debian)? What I'm not sure about is if that causes other versions of the
library to blow up (and unfortunately don't have any to hand right now to
test).

  reply	other threads:[~2019-12-07 19:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 17:15 Adam Thompson
2019-12-07 18:43 ` Dominique Martinet
2019-12-07 19:01   ` Alfonso S. Siciliano
2019-12-07 19:34     ` Dominique Martinet
2019-12-07 19:49       ` Adam Thompson [this message]
2019-12-07 21:45         ` alf.siciliano
2019-12-07 22:16           ` Dominique Martinet
2019-12-08  2:29             ` Geoff McLane
2019-12-08  3:56               ` Karl Dahlke
2019-12-08  8:08                 ` Alfonso Sabato Siciliano
2019-12-08  8:07               ` Dominique Martinet
2019-12-08 13:22               ` Adam Thompson
2019-12-08 21:22                 ` Geoff McLane
2019-12-07 19:44     ` Adam Thompson

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=20191207194928.GD194728@toaster \
    --to=arthompson1990@gmail.com \
    --cc=asmadeus@codewreck.org \
    --cc=edbrowse-dev@edbrowse.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 NNTP newsgroup(s).