On Tue, 2019-11-19 at 16:15 -0500, Frank Ch. Eigler wrote:
> Hi -
>
>
> > [...] What I want is simply make it easy for the user to say where
> > they expect the sources are. So there is no surprises.
>
> If this were a mandate, it would be a hassle, for any build that's
> more than one directory
Hi -
> I am simply interested in knowing what is done for outgoing https
> connections to be authenticated. What would it take to use the trust
> roots for validating the server certificates?
OK, I misunderstood. Certificate-authority certificates in the trust
root (compiled-in directories) serv
Hi,
On Tue, 2019-11-19 at 16:22 -0500, Frank Ch. Eigler wrote:
> On Tue, Nov 19, 2019 at 09:15:20PM +0100, Mark Wielaard wrote:
> > > That's what the doc says. What the code does, as far back as the year
> > > 2001, is have a static flag/counter in curl_global_init() that
> > > prevents multiple
https://sourceware.org/bugzilla/show_bug.cgi?id=25173
--- Comment #7 from Milian Wolff ---
hmm but in perfparser we have a workaround for missing aranges... I'll have to
dig into this to see why it doesn't work here.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=25173
--- Comment #8 from Mark Wielaard ---
(In reply to Milian Wolff from comment #7)
> hmm but in perfparser we have a workaround for missing aranges... I'll have
> to dig into this to see why it doesn't work here.
You also mention it is an issue
Hi -
> But it isn't just about interference with other libcurl activity. If
> you look at the curl_global_init code you see that it actually calls
> a lot of code in other libraries. It is the curl_global_init code
> that shouldn't be run in a multi-threaded environment. That it is
> acceptable to
