Federico Di Pierro

Results 943 comments of Federico Di Pierro

So, we need to disable the build with shared libelf, because `zig` statically links all specified libraries; see: https://github.com/ziglang/zig/issues/7094 Indeed the CI complains it cannot find system libelf. Since this...

Now failing the build on > ld.lld: error: undefined symbol: arc4random_buf >>> referenced by ares_rand.c:270 That's probably because c-ares does some magic to detect that symbol: https://github.com/c-ares/c-ares/blob/main/CMakeLists.txt#L456; that symbol was...

I tried to build `c-ares` from scratch (ie: without Falco involved at all) with `zig` and it worked fine with the same `export`s we are doing in the CI.

Update: i saw that updating c-ares to 1.33.1 (latest release) fixed the issue. I am going to bump it in libs (if possible, ie: if grpc does not complain :/...

So, i now bumped this branch to use libs [`chore/zig_build` branch HEAD](https://github.com/falcosecurity/libs/tree/chore/zig_build); that is a branch i pushed upstream with all zig related fixes on it: * https://github.com/falcosecurity/libs/pull/2034 * https://github.com/falcosecurity/libs/pull/2036...

To be able to build Falco, for now, i had to disable `_FORTIFY_SOURCE`, see my commit message: 0bb6f49e64c18936df19b321df10e862cb6259e4 I opened an upstream issue to track the problem: https://github.com/ziglang/zig/issues/21252 and a...

So, we now have artifacts working (passing tests too!); here are the differences for arm64: * normal Falco: ``` ldd falco linux-vdso.so.1 (0x0000e4ff9035f000) libelf.so.1 => /lib/aarch64-linux-gnu/libelf.so.1 (0x0000e4ff902f0000) librt.so.1 => /lib/aarch64-linux-gnu/librt.so.1...

The PR is ready; idea is to merge this right after the Falco release, after https://github.com/falcosecurity/libs/pull/2034, https://github.com/falcosecurity/libs/pull/2037 and https://github.com/falcosecurity/libs/pull/2049 are merged in Falco libs (i'll then take care of update...