Alec Leamas

I have applied patch above to the Debian wxsvg package. Please consider this as a request to apply this patch.

I have applied patch above to the Debian wxsvg package. Please consider this as a request to apply this path (where are the sources?)

python module: wrong installation path

Hi, wxsvg seems to use some c++ atomic stuff. Sometimes, these functions lives in a separate -latomic library which needs to be linked. However, current configuration does not take this into account. This causes build errors on some esoteric Debian platforms like sh4, see https://buildd.debian.org/status/fetch.php?pkg=wxsvg&arch=sh4&ver=2%3A1.5.22%2Bdfsg.1-1&stamp=1634298153&raw=0 I'm adding enclosed patch to the next Debian packaging. To me it looks safe and should not break any eggs. OTOH, they...

Handle platforms with separate -latomic library

configure: handle separate -latomic library.

This has been been discussed, but rejected for various reasons. The alternative to SF would have been gitlab rather than github, though. As for commits-as-patches I assume you can get around it by cloning the repo and then use git cherry-pick or git format-patch depending on your use case?

A bit short of time right now. That said, since lirc_options.conf exists your lirc version is reasonably updated. Furthermore, since you are referring to hardware.conf you might be using outdated guide, hardware.conf is not used since long. I have no idea about /boot/config.txt, thsi is raspberry stuff above my paygrade. I'd suggest that you look into the upstream docs at https://www.lirc.org/html/configuration-guide.html