Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiling under Fedora 20/libcurl 7.32.0 doesn not work #50

Closed
rubdos opened this issue Jun 1, 2015 · 6 comments
Closed

Compiling under Fedora 20/libcurl 7.32.0 doesn not work #50

rubdos opened this issue Jun 1, 2015 · 6 comments

Comments

@rubdos
Copy link
Contributor

rubdos commented Jun 1, 2015

/home/rsmet/src/sf.net/githubpp/curlcpp/include/curl_easy.h:280:31: error: ‘CURLOPT_DEPRECATED72’ was not declared in this scope
         CURLCPP_DEFINE_OPTION(CURLOPT_DEPRECATED72, long);
                               ^
/home/rsmet/src/sf.net/githubpp/curlcpp/include/curl_easy.h:47:33: note: in definition of macro ‘CURLCPP_DEFINE_OPTION’
     template <> struct option_t<opt> {\
                                 ^
/home/rsmet/src/sf.net/githubpp/curlcpp/include/curl_easy.h:47:36: error: template argument 1 is invalid
     template <> struct option_t<opt> {\
                                    ^
/home/rsmet/src/sf.net/githubpp/curlcpp/include/curl_easy.h:280:9: note: in expansion of macro ‘CURLCPP_DEFINE_OPTION’
         CURLCPP_DEFINE_OPTION(CURLOPT_DEPRECATED72, long);

Apparently, the #if defined(LIBCURL_VERSION_NUM) && LIBCURL_VERSION_NUM > 0x072500 block fails, but commenting out so it will define the CURLOPT_OBSOLETE72 doesn't work either.

Any clue? I first tried as a submodule, but compiling it like in the README gives the same error.

@dkleissa
Copy link

dkleissa commented Jun 2, 2015

I'm having the same issue on OSX 10.9.5

@JosephP91
Copy link
Owner

Mmm, I'm trying to figure it out. @susnux can I ask your opinion? Any clue?

susnux added a commit to susnux/curlcpp that referenced this issue Jun 2, 2015
@susnux
Copy link
Contributor

susnux commented Jun 2, 2015

Yes there was a mistake, it is called OBSOLETE72 in 37.1 and later.
Before it is called CLOSEPOLICY (this option was never implemented in cURL and never had any effect).

@JosephP91
Copy link
Owner

@dkleissa can you check if this commit solved your issue? Thank you!

@rubdos
Copy link
Contributor Author

rubdos commented Jun 3, 2015

For me this solves the issue. Thank you :)

@JosephP91
Copy link
Owner

@rubdos Good. If @dkleissa was having the same issue, I suppose the commit definitely solved it. So you can close it.

@rubdos rubdos closed this as completed Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants