Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61116 - Suggest removing --enable-seccomp in build()
Attached to Project:
Arch Linux
Opened by Johannes Ernst (jernst) - Tuesday, 18 December 2018, 00:17 GMT
Last edited by Levente Polyak (anthraxx) - Tuesday, 18 December 2018, 01:27 GMT
Opened by Johannes Ernst (jernst) - Tuesday, 18 December 2018, 00:17 GMT
Last edited by Levente Polyak (anthraxx) - Tuesday, 18 December 2018, 01:27 GMT
|
DetailsWith this flag, my memcached for Decko [1] refuses to respond after a while, with the process changing from
memcach+ 2540 1.0 0.0 414788 3200 ? Ssl 18:28 0:00 /usr/bin/memcached -l 127.0.0.1 -p 6001 -o modern to memcach+ 2540 0.0 0.0 0 0 ? Zsl 18:28 0:00 [memcached] <defunct> It works without that build flag. I'm not the only one who seems to have run into this: [2][3] and the memcached people seem to have acknowledged [4] that there may be issues at least on ARM. My problem is on x86_64 however. [1] https://decko.org/ [2] https://forum.manjaro.org/t/memcached-not-starting-systemctl-reporting-it-is/49038/3 (bottom) [3] https://archlinuxarm.org/forum/viewtopic.php?t=12902&p=58822 [4] https://github.com/memcached/memcached/issues/384 |
This task depends upon
Closed by Levente Polyak (anthraxx)
Tuesday, 18 December 2018, 01:27 GMT
Reason for closing: Upstream
Tuesday, 18 December 2018, 01:27 GMT
Reason for closing: Upstream
report your exact problems and traces upstream