edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] building on ubuntu
Date: Mon, 2 Sep 2019 09:13:00 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1909020910430.37989@phoenix> (raw)
In-Reply-To: <20190802032734.eklhad@comcast.net>


I'm glad we have a little knowledge base going so it can become easier in 
the future. I remember you were writing about this a while ago.


On Mon, 2 Sep 2019, Karl Dahlke wrote:

> 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
> 	        curl https://weloveanimals.me
> 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.
>
> Karl Dahlke
>

  reply	other threads:[~2019-09-02 16:13 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
2019-09-02 16:13   ` Kevin Carhart [this message]
2019-09-02 19:24     ` Geoff McLane
2019-09-03  0:17       ` Karl Dahlke
2019-09-03  5:52         ` Dominique Martinet

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=alpine.DEB.2.21.1909020910430.37989@phoenix \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).