curl / Mailing Lists / curl-library / Single Mail


Re: Built curl with nghttp2, attempts at HTTP2 return unsupported protocol

From: Reese Grimsley <>
Date: Mon, 27 Mar 2017 18:05:01 -0500

Problem is fixed. I rebuilt the library, but even though I ensured every
file in my compiler's folders were replaced with the right versions, it
still would not show that it was using a libcurl version with nghttp2. I
made a new project in CodeBlocks, and that was enough to fix the problem.
Thanks for the help

On Mon, Mar 27, 2017 at 3:56 PM, Reese Grimsley <> wrote:

> Your were correct, the curl version being used was not the one that I
> intended it to be. It was using the first build I made that used OpenSSL
> 1.0.2 and no nghttp2. I am having difficulties now getting my compiler
> (mingw32 in Codeblocks) to recognize that I am using a different version of
> the library. My program should only use the library I specifically link to
> it, correct? The linker settings ask for .a or .lib files, but would it
> work/be better to use .dll when possible? I told my IDE to use the .a and
> .dll files from the lib/.libs folder, but it still seems to give me the
> version of the past build. Running a msys2 shell of mingw32 shows the
> correct version of curl.exe. I will rebuild libcurl in case I overwrote
> some file with an older copy accidentally. Thanks for the help.
> On Mon, Mar 27, 2017 at 11:44 AM, Ray Satiro via curl-library <
>> wrote:
>> On 3/27/2017 10:39 AM, Reese Grimsley wrote:
>> > I built curl/libcurl with nghttp2 (at least I believe I did), and when
>> > I
>> > try curl_easy_setopt(curl,CURLOPT_HTTP_VERSION,CURL_HTTP_VERSION
>> > it returns the error for unsupported protocol. Is there a way that I
>> > can check to see if nghttp2 was actually built correctly into my
>> > libcurl? I ran make test after the initial make, and only about 6
>> > tests failed. I am positive that the configure file was set to enable
>> > nghttp2, but if it is possible to build libcurl with an invalid
>> > nghttp2 build, then that could also be the problem. Thanks.
>> If you're linking to libcurl as a shared object (eg DLL in Windows) it's
>> possible that a different libcurl is being loaded instead of the one you
>> expect. Use curl_version() to see the libraries it's using,
>> printf("%s\n", curl_version());
>> You can also do it programmatically
>> if(!(curl_version_info(CURLVERSION_NOW)->features &
>> /* problem */
>> }
>> -------------------------------------------------------------------
>> Unsubscribe:
>> Etiquette:

Received on 2017-03-28