FS#71299 - [ngrep] does not use pcre due to configure bug
Attached to Project:
Community Packages
Opened by loqs (loqs) - Saturday, 19 June 2021, 16:58 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 03 September 2023, 16:08 GMT
Opened by loqs (loqs) - Saturday, 19 June 2021, 16:58 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 03 September 2023, 16:08 GMT
|
Details
Description:
The configure test would always fail due to [1] preventing pcre from being detected and using a bundled regex library instead. Tested with [2]. Additional info: * ngrep 1.47-2 [1] https://github.com/jpr5/ngrep/commit/b8b1e9751e1d074af0dd77c2554c1b25fd8f7abe [2] PKGBUILD.diff Steps to reproduce: ldd /usr/bin/ngrep | grep pcre produces no output |
This task depends upon
Closed by Jelle van der Waa (jelly)
Sunday, 03 September 2023, 16:08 GMT
Reason for closing: Fixed
Additional comments about closing: 1.47-4
Sunday, 03 September 2023, 16:08 GMT
Reason for closing: Fixed
Additional comments about closing: 1.47-4
Use glibc's regex [2].
Use pcre2 [3]. The upstream PR [4] has not been merged. There have been no upstream commits since January 2019 [5].
[1] https://pcre.org/
[2] PKGBUILD.diff.1
[3] PKGBUILD.diff.2
[4] https://github.com/jpr5/ngrep/pull/27
[5] https://github.com/jpr5/ngrep/commit/2a9603bc67dface9606a658da45e1f5c65170444
PKGBUILD.diff.2 (10.5 KiB)