Trying to fix cross-build error for current fsearch version

[gc-user]

I'd like to make a PR to update the fsearch package, but since v3 there's a cross-build error that results in all cross-builds to fail, making the PR essentially impossible.

The error message is

meson.build:19:32: ERROR: Can not run test applications in this cross environment.

It seem to be these lines in meson.build that cause the issue:

# Check if the build platform supports using malloc_trim
malloc_trim_support_result = cc.run(
  '''
    #include <malloc.h>

    int main (int argc, char *argv[]) {
      malloc_trim(0);
      return 0;
    }
  ''',
  name : 'malloc_trim is supported on the build platform',
)

if malloc_trim_support_result.compiled() and malloc_trim_support_result.returncode() == 0
  have_malloc_trim = true
else
  have_malloc_trim = false
endif

# Check if the build platform supports using fanotify without the CAP_SYS_ADMIN capability
fanotify_support_result = cc.run(
  '''
    #include <sys/fanotify.h>
    #include <fcntl.h>

    int main (int argc, char *argv[]) {
      int fd = fanotify_init (FAN_CLOEXEC|FAN_CLASS_NOTIF|FAN_REPORT_DFID_NAME, O_RDONLY);
      return fd < 0 ? 1 : 0;
    }
  ''',
  name : 'fanotify is supported by the build platform and works without CAP_SYS_ADMIN capabilities',
)

if fanotify_support_result.compiled() and fanotify_support_result.returncode() == 0
  have_fanotify = true
else
  have_fanotify = false
endif

# Check if the build platform supports inotify
inotify_support_result = cc.run(
  '''
    #include <sys/inotify.h>
    #include <fcntl.h>

    int main (int argc, char *argv[]) {
      int fd = inotify_init1(IN_NONBLOCK);
      return fd < 0 ? 1 : 0;
    }
  ''',
  name : 'inotify is supported by the build platform',
)

if inotify_support_result.compiled() and inotify_support_result.returncode() == 0
  have_inotify = true
else
  have_inotify = false
endif

If I reduce the lines to

have_malloc_trim = true

have_fanotify = true

have_inotify = true

the cross-build (I tested aarch64) run through fine.

As I'm not a dev / coder I'm not sure if this "brute-force" approach is the way to go or if the check should only be disabled for cross-builds, which would probably require a if then addition instead of that massive code reduction and fixed setting of the respective options.
And maybe, if fixed is the way to go, false instead of true should be set?

[classabbyamp]

try adding the qemu build_helper

[gc-user]

Thanks for the reply and tip. That one did the trick!

For future reference / me:

I added the line

build_helper="qemu"

after the build_style line.