From: Karl Dahlke <email@example.com>
Subject: [edbrowse-dev] building on ubuntu
Date: Mon, 02 Sep 2019 03:27:34 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
This isn't the problem Geoff was running into; his is much easier to deal with.
I know the one you're talking about though; see the README file line 73.
You don't need edbrowse to diagnose it; a ssimple test is
You get the website or the communication error.
curl doesn't fail on too many websites, but if it's the one you really want to go to, well ...
And obviously edbrowse can't do a thing about it.
I'll add your notes to the README on rebuilding curl from source, if people want to do that, and even I might,
cause I also have one of those unfortunate distributions where curl is bound to gnutls instead of openssl.
next prev parent reply other threads:[~2019-09-02 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 6:32 Kevin Carhart
2019-09-02 7:27 ` Karl Dahlke [this message]
2019-09-02 16:13 ` Kevin Carhart
2019-09-02 19:24 ` Geoff McLane
2019-09-03 0:17 ` Karl Dahlke
2019-09-03 5:52 ` Dominique Martinet
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).