I am compiling 14.1.4 packages for Slackware 15.0. ktorrent fails to build with the following fatal error:
ktorrent-trinity-14.1.4/src/libktorrent/torrent/cachefile.cpp:44:10: fatal error: settings.h: No such file or directory
I'm using cmake.
Appreciate some help. Thanks.
Darrell Anderson via tde-devels wrote:
I am compiling 14.1.4 packages for Slackware 15.0. ktorrent fails to build with the following fatal error:
ktorrent-trinity-14.1.4/src/libktorrent/torrent/cachefile.cpp:44:10: fatal error: settings.h: No such file or directory
I'm using cmake.
I've created a PR that fixes the issue on my machine, are you able to give it a go? You should be able to download the patch (also attached) and apply it to the r14.1.x branch with no issue.
PR: https://mirror.git.trinitydesktop.org/gitea/TDE/ktorrent/pulls/35 PATCH: https://mirror.git.trinitydesktop.org/gitea/TDE/ktorrent/pulls/35.patch
mio
On 5/9/25 10:10 PM, mio via tde-devels wrote:
I've created a PR that fixes the issue on my machine, are you able to give it a go? You should be able to download the patch (also attached) and apply it to the r14.1.x branch with no issue.
I found the updated patch and applied. The package now compiles. Thank you. I am not a torrent user and can't check usability.
From an educational perspective, I'd like to learn how something like this slips through the cracks. Seems something like this should have been obvious right away? Is this a distro specific kind of failure?
Dne so 10. května 2025 19:25:06 Darrell Anderson via tde-devels napsal(a):
On 5/9/25 10:10 PM, mio via tde-devels wrote:
I've created a PR that fixes the issue on my machine, are you able to give it a go? You should be able to download the patch (also attached) and apply it to the r14.1.x branch with no issue.
I found the updated patch and applied. The package now compiles. Thank you. I am not a torrent user and can't check usability.
From an educational perspective, I'd like to learn how something like this slips through the cracks. Seems something like this should have been obvious right away? Is this a distro specific kind of failure? ____________________________________________________
This problem is certainly not distribution-dependent. Setting dependencies between targets is important to ensure reliable builds when using multiple cores. It was a lucky coincidence that the problem did not manifest itself during the build of the official packages. Sometimes it can be challenging to look for such problems because they can occur randomly. It was good that you managed to catch the problem.
Cheers Slávek --