Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16078] New: ClamAV: FD_PASSING test fails when it should not.
Date: Fri, 17 May 2024 03:31:37 +0000	[thread overview]
Message-ID: <bug-16078-163@https.bugs.busybox.net/> (raw)

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: unassigned@buildroot.uclibc.org
          Reporter: craig.anderson@instrumental.com
                CC: buildroot@uclibc.org
  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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-05-17  3:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  3:31 bugzilla [this message]
2024-06-15 15:21 ` [Buildroot] [Bug 16078] ClamAV: FD_PASSING test fails when it should not bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-16078-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox