edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Curl library error
Date: Thu, 01 Feb 2018 13:08:30 -0500	[thread overview]
Message-ID: <20180101130830.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1802010449280.1929@debian.pulsar.com>

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

Chuck ran:
> git checkout df7c3d74890026fc1acbfabdbb5a7b82c12cbc4d

That build is as of Jan 14.  Do this.

git log -40 >/tmp/logs

That gives a summary of the last 40 commits.
Find the one you used df7c3d74890026fc1acbfabdbb5a7b82c12cbc4d
and note its date Jan 14.
So you are running as of Jan 14.
You can roll back to any commit on any date.
But it sounds like edbrowse as of Jan 14 still fails today, though you believe it did not fail on Jan 14.
That does not 100% let me off the hook, I still might have a problem somewhere that was uncovered by a newer version of curl or some such, software is complicated.
You might check your packages to see if curl or libcurl or libcurl-devel has been upgraded since then,
particularly if one of libcurl or libcurl-devel was upgraded and not the other.
Of course these are fedora names of packages, not sure about your package manager.
Maybe someone on arch or debian can help you with this.
Possibly the library got auto-updated and not the corresponding header files, making them out of sync.
Or maybe just check time stamps with ls for /bin/curl, /lib/libcurl.so, and /usr/include/curl/curl.h.

Karl Dahlke

      parent reply	other threads:[~2018-02-01 18:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 12:09 Chuck Hallenbeck
2018-01-29 14:06 ` Karl Dahlke
2018-01-29 15:19   ` Chuck Hallenbeck
2018-01-29 15:27   ` Chuck Hallenbeck
2018-01-29 16:03 ` Karl Dahlke
2018-01-29 16:53   ` Chuck Hallenbeck
2018-01-29 17:37     ` Dominique Martinet
     [not found] ` <alpine.DEB.2.21.1802010449280.1929@debian.pulsar.com>
2018-02-01 18:08   ` Karl Dahlke [this message]

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=20180101130830.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).