Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes github issue #213: Problem compiling with libupnp 1.14.0 UpnpInit() has long been deprecated and has been dropped in 1.14.0. Use UpnpInit2() instead.
- Loading branch information
Showing
2 changed files
with
7 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8784480
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build fails:
https://github.com/amule-project/amule/runs/1028728927
8784480
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Compiled ok here with gcc 10, at least I thought so.
Anyway, I'll fix it.
8784480
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me with GCC 9.3.0 the patch works perfectly well and amule master compiles and installs OK...
And isn't the error cited above done with libupnp version 1.6.24? ->
checking for libupnp version >= 1.6.6... yes (version 1.6.24)
8784480
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi PhobosK,
UpnpInit() was already deprecated in the 1.6.x branch of libupnp, so there was already UpnpInit2() in that version of the library. There should be no problem with that.