Well, frankly, I'd very much prefer to have a patch fixing the source code so it compiles on a newer compiler without warnings, rather than back-dating the compiler.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also prefer that, but this is the smallest step with the least amount of risk.
When I have time I'll have a stab at a bigger patch if someone is willing to review and apply it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm willing to review and apply a patch, but my C++ knowledge (in particular regarding modern C++) is close to 0, so without a lot of Internet research, I wouldn't know how to fix that properly right now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A temporary solution was found to be to change the C++ compile version to be C++ 14.
On Arch Linux, for building this package from the AUR the solution is to add
to the top of the
build()function inPKGBUILD.From this, I can venture a guess to say that AVaRICE just needs to be updated to support C++17.
I've created a small patch to specify an older C++ standard.
Well, frankly, I'd very much prefer to have a patch fixing the source code so it compiles on a newer compiler without warnings, rather than back-dating the compiler.
I also prefer that, but this is the smallest step with the least amount of risk.
When I have time I'll have a stab at a bigger patch if someone is willing to review and apply it?
I'm willing to review and apply a patch, but my C++ knowledge (in particular regarding modern C++) is close to 0, so without a lot of Internet research, I wouldn't know how to fix that properly right now.
Fixed by patch #40