Summary: | net-p2p/transmission-remote-gui: Fails to start when W^X protection is activated | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Andrey Korobkov <alster> |
Component: | Individual Port(s) | Assignee: | Jose Alonso Cardenas Marquez <acm> |
Status: | Open --- | ||
Severity: | Affects Some People | CC: | alster, vsasjason |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(acm) |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Andrey Korobkov
2021-05-18 05:45:25 UTC
(In reply to Andrey Korobkov from comment #0) Hi, maybe the main reason could be fpc/lazarus use syscalls and if I'm not mistaken this kind of protection avoid this kind of procedures. But fpc/lazarus have a FPC_USE_LIBC option for use LIBC instead of direct syscalls. I don't know if it is well updated and maybe it could break somethings (In reply to Jose Alonso Cardenas Marquez from comment #1) Hi and thank you for your time and advice! While I've moved from transmission-remote-gui to stig (python-based TUI), I still would like to help other people who still use it. Now I'm going my first steps in patching and creating new ports, and I like this process alot. So I may try to fix this port, just let me learn some more things about proper porting workflow (patching, building, linting, testing, submitting, etc). People here are really kind and very helpful! :) And I hope to learn all the needed skills to help them and be useful for the community. |