walnascar and whinlatter support

[zboszor]

No description provided.

[ajlennon]

Seems to be failing

[zboszor]

Seems to be failing

Yes, but what? All CI tasks seem to be stuck in "queued" as far as I can see.

FWIW, I can start my build locally now, and there are no more has a lack of whitespace around the assignment warnings coming from meta-mono recipes.

[ajlennon]

Yes I restarted the box and there's some very strange sstate error. Maybe I need to wipe out the sstate

[ajlennon]

fwiw it is building here for some reason

https://github.com/DynamicDevices/meta-mono/actions/runs/14702446718

[ajlennon]

Killed the sstate and re-ran. Something strange going on. First build works and second doesn't. Am wondering if the first build is polluting something?

https://github.com/DynamicDevices/meta-mono/actions/runs/14969532368/job/42060720344

[zboszor]

I get this under current Yocto master:

| mkdir -p build-shared
| (cd build-shared && CC="gcc " CXX="g++ " "/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/recipe-sysroot-native/usr/bin/cmake" -D CMAKE_MAKE_PROGRAM="/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/recipe-sysroot-native/usr/bin/make" -D CMAKE_INSTALL_PREFIX:PATH="/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/recipe-sysroot-native/usr" -D BTLS_ROOT:PATH="/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/sources/mono-6.12.0.206/external/boringssl" -D SRC_DIR:PATH="/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/sources/mono-6.12.0.206/mono/btls" -D BTLS_CFLAGS:STRING="-isystem/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/recipe-sysroot-native/usr/include "  -DBTLS_ARCH="x86_64" -DBUILD_SHARED_LIBS=1 "/mnt/zozo/yocto-5.3-arm/tmp-sicom/work/x86_64-linux/mono-native/6.12.0.206/sources/mono-6.12.0.206/mono/btls")
| CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
|   Compatibility with CMake < 3.5 has been removed from CMake.
| 
|   Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
|   to tell CMake that the project requires at least <min> but has been updated
|   to work with policies introduced by <max> or earlier.
| 
|   Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
| 
| 
| -- Configuring incomplete, errors occurred!
| make[3]: *** [Makefile:684: build-shared/Makefile] Error 1

I will have to patch the btls build so it may work with cmake 4.0 in Yocto master.

EDIT: Apparently, the "Framework Mono" (renamed so when Mono was pulled under the Wine project umbrella) version 6.14.1 has modified the CMake minimum version requirements for at least btls, so it may have a chance to build under Yocto 5.3. See https://gitlab.winehq.org/mono/mono/-/releases

[ajlennon]

Not sure why it's not picking up the CI - closing and reopening to try to trigger

[ajlennon]

Not sure why this isn't picking up - the action runner is online and connected - just rebooted the CI box. Bit caught up at the moment but will try to look later

[zboszor]

@ajlennon Apparently, there are a few fixes at https://gitlab.winehq.org/mono/mono/-/tree/main for arm64 that needed backporting to the 6.14 branch. Can you please trigger the CI in case it went haywire again? Thanks.

[ajlennon]

Done

[ajlennon]

I dunno if you can do this but if you can close and repoen the PR this is what I do and should (I think) trigger the CI

[zboszor]

Closing / reopening does not seem to work for me.

FWIW, styhead vs arm/arm64 is likely to get stuck. Not sure if it's your CI box or what actually causes it. I can build mono-native and mono just fine on my buildboxes.

Anyway, I pushed a new commit to omit styhead from the CI test matrix, so it's walnascar and master only for now.