New: ClamAV: FD_PASSING test fails when it should not.
https://bugs.busybox.net/show_bug.cgi?id=16078
Bug ID: 16078
Summary: ClamAV: FD_PASSING test fails when it should not.
Product: buildroot
Version: 2024.02
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]Target Milestone: ---
In ClamAV, there is a CMake test for whether or not the system supports FD_PASSING.
In the file CheckFDPassing.cmake, on line 77:
if("${test_compile_result}" AND ("${test_run_result}" EQUAL 0))
This fails on:
- Host running Ubuntu 22.04 on a late model Intel PC (x86-64).
- Target is the same as the host.
because $test_run_result is "ON", not 0. $test_run_result is 0 when ClamAV is compiled on the same build machine, but outside of Buildroot.
My workaround is to change the line to:
if("${test_compile_result}" AND (("${test_run_result}" STREQUAL "ON") OR (("${test_run_result}" EQUAL 0))))
which just accept "ON" as passing.
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 16078] ClamAV: FD_PASSING test fails when it should not.
https://bugs.busybox.net/show_bug.cgi?id=16078
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
CC| |[email protected]
Status|NEW |RESOLVED--- Comment #1 from Yann E. MORIN <[email protected]> --- Thank you for your report.
The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues
We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker.
Thank you!
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot