detected compiler gcc '11.4.0' (['cc']), linker: ld.bfd (['ld.bfd']), static_linker: ar (gcc) (['ar'])
/home/runner/work/rizin/rizin/subprojects/pcre2_cross_native.wrap:1:1: warning previous provide for 1330 from 2356, is being overridden by 2361
  1 | [wrap-git]
      ^
configuring 'rizin', version: v0.8.0
message: rizin lib version: 0.8 
c compiler: supports argument '--std=gnu99': YES
c compiler: supports argument '-Werror=sizeof-pointer-memaccess': YES
c compiler: supports argument '-Wimplicit-fallthrough=3': YES
Cloning into '/home/runner/work/rizin/rizin/subprojects/capstone-next'...
HEAD is now at b4fde983 [PPC] Expose instruction formats (#2276)
[capstone-next] entering subproject 'capstone-next'
muon: ../src/datastructures/arr.c:98: arr_get: Assertion `i < arr->len' failed.
/home/runner/work/rizin/rizin/meson.build:186:21: error encountered unhandled error
186 |     capstone_proj = subproject('capstone-' + capstone_version, default_options: ['default_library=static'])
                          ^______________________________________________________________________________________
/home/runner/work/_temp/4bc8ab07-d736-4edd-825d-012f546a09e2.sh: line 1:  3217 Aborted                 (core dumped) muon setup build

See this meson file: https://github.com/rizinorg/rizin/blob/dev/meson.build

~lattis, sorry, still didn't help: https://github.com/rizinorg/rizin/actions/runs/7076647158/job/19260119164?pr=3345#step:9:73

Have there been any updates on this issue?

Changed to pass -print-search-dirs. ~xvilka, can you confirm this fixes the tcc issue?

@~xvilka no news on this ?

@~xvilka look at line 316 in compiler.c:

https://git.sr.ht/~lattis/muon/tree/master/item/src/compilers.c#L313

you can try to fix tinycc here with the correct option to pass to tinycc.

Ah, we use our patched fork for that: https://github.com/ret2libc/meson.git There was a PR (https://github.com/mesonbuild/meson/pull/8248) to meson but it was never accepted, so we decided it will be easier to just completely move to Muon for this configuration.

When we try build Rizin with Muon + TinyCC it can't find the necessary library, while Meson can:

/home/runner/work/rizin/rizin/meson.build:354:33: error library not found
354 |     it_lrt = it_cc.find_library('rt', required: true, static: is_static_build)
                                      ^
/home/runner/work/rizin/rizin/meson.build:354:20: error in method compiler.find_library()
354 |     it_lrt = it_cc.find_library('rt', required: true, static: is_static_build)
                         ^
Error: Process completed with exit code 1.

See PR at https://github.com/rizinorg/rizin/pull/3345

Take the following use case:

1. Due to some external error, e.g. network problem build triggered via hottub fails.
2. If we restart the build manually on Sourcehut, it finishes successfully
3. But the GitHub doesn't receive an updated status, that it was a successful build from the second try, not a failure anymore.

It fails with missing i18n, I will send a patch to QEMU shortly

meson.build:4:8: error module 'i18n' is unimplemented,
  If you would like to make your build files portable to muon, use `import('i18n', required: false)`, and then check the .found() method before use.
  4 |   i18n.gettext(meson.project_name(),
             ^
qemu/meson.build:3640:3: error in function subdir()
3640 |   subdir('po')
         ^