From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 22DBA791CA for ; Sat, 7 Dec 2019 19:56:04 -0800 (PST) Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id dncni73NVWWx4dnfvietw5; Sun, 08 Dec 2019 03:56:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1575777363; bh=snwzkK6Kikws1Jzl/+R3kFeS0ingHXcN5ilWksl/SwQ=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=dEipUTGZxkFHop7DA+Qx+mvWS3MU1ZVwsAJN4Y5NxJhA9gJieIt4VR1D+u6AOhyrQ 6di5S1TXU4l+j/FY1hFLHif/HMZ3CZu+j+Dm4EydxbeFzx/ZCJ2bw+BD8EbdDNEsTv 5HOn31DPTH7suCysAEMBbm6ywOXlO4NU36Y2zvpo+tnpt2FDmnz7OZB1DWyBQTRajy WyB1f+JIiKZRSOoNWh41L6iQZJ1L0XQO70CIMAJajFBQgMV4y+FZzs+RpDI1tKwdgw nqKXOsV74ccqsgd1/HVc4Yn+wtFNi6FjLB4HBQr+V9YCa/FMkqrzMtBv/Trckyw285 aM8P1tE05sg0w== Received: from unknown ([IPv6:2601:408:c300:a3d0:21e:4fff:fec2:a0f1]) by resomta-ch2-18v.sys.comcast.net with ESMTPSA id dnftit9eMMnKldnfuiK1iq; Sun, 08 Dec 2019 03:56:03 +0000 X-Xfinity-VMeta: sc=0.00;st=legit To:edbrowse-dev@edbrowse.org, alf.siciliano@gmail.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20191207171534.GA194728@toaster> User-Agent: edbrowse/3.7.6 Subject: [edbrowse-dev] tidySetOptBool vs tidySetOptInt on debian Date: Sat, 07 Dec 2019 22:56:01 -0500 Message-ID: <20191107225601.eklhad@comcast.net> X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nextpart-eb-648386 Content-Transfer-Encoding: 7bit This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --nextpart-eb-648386 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi folks, Writing software for various systems and platforms is challenging, but = tidy has done it, duktape has done it, and I'm sure we can too. I'm 99% sure the recent tidy comfusion is incompatibility between = headers and linked in library. This is sometimes caused by distros that already have tidy, but an = older version, so a packager brings in a new version and builds and = that's fine but then there are two such libraries, if he doesn't remove the old one, and one can glom on to the old = library, and just anything can happen after that. > I am very alarmed by the 'findTidy.cmake' change - I can remove these lines if you wish, I am the arbiter, is there another approach that might work better for these bsd folks? I will mostly stay out of the middle of this one and you can = collectively advise me. One thing we recommend is when you must bring in a newer tidy to build = edbrowse you *have* to delete the old one and make the new one the only = tidy in the distro, then of course that will be the only one cmake can = find and there shouldn't be trouble. It is clear that the thread type is suppose to be opaque, and accessed = only through api, so I changed to pthread_equal as you suggest. Karl Dahlke --nextpart-eb-648386--