From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] ifndef CURLE_PEER_FAILED_VERIFICATION
Date: Wed, 06 Aug 2014 10:14:26 -0400 [thread overview]
Message-ID: <20140706101426.eklhad@comcast.net> (raw)
Your analysis is correct.
We are redefining these things to different numbers here - bad news.
The comment says these definitions are there for older
versions of curl that don't have them,
but honestly we don't support older versions of curl.
We gave up on that a while ago.
You just have to be up to date with curl, pcre, smjs, etc.
So I suggest we just delete this stuff.
I took it out and it builds and runs just fine.
Chris I think you put those in, what do you think?
If nobody objects I'll push the change and delete these lines
that, unintentionally, redefine two curl constants.
Karl Dahlke
next reply other threads:[~2014-08-06 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 14:14 Karl Dahlke [this message]
2014-08-06 17:19 ` Chris Brannon
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 18:39 Karl Dahlke
2014-08-06 13:54 Paul Onyschuk
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=20140706101426.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).