~freedwu 8 months ago

Comes from https://github.com/termux/termux-packages/pull/19733

~lattis 7 months ago

It looks like this issue is with building https://github.com/JCWasmx86/mesonlsp which appears to use a fork of muon? If so can you try an repro this bug on muon master?

JCWasmx86@t-online.de 7 months ago · edit

Hello.

I'm the author of mesonlsp. I just split up muon into a muon executable and a libmuon for usage in my language server for formatting. (If wished, I can upstream it)

I think it's an issue with the upstream muon buildsystem.

• Here: https://github.com/annacrombie/muon/blob/69a5d423ed63ab2e5dd113ffa0d8c692953d2981/meson.build#L39 You check, whether it's a UNIX-like system (No android is listed here)

• This goes to https://github.com/annacrombie/muon/blob/69a5d423ed63ab2e5dd113ffa0d8c692953d2981/meson.build#L54: You check if the platform is not windows and print a warning

• See here: https://github.com/termux/termux-packages/actions/runs/8657067879/job/23738605764?pr=19733: muon| ../src/subprojects/muon/meson.build:54: WARNING: configuring muon for an unsupported platform "android" => android is not supported, platform = "null"

• Here: https://github.com/annacrombie/muon/blob/master/src/platform/meson.build#L14 you iterate over an array with filenames, building platform / filename.

• The file null/filesystem.c does not exist. If I look into posix/, I can see like 10 files. If I look into windows/, I can see 11 files. If I look into null/ I only see one file.

So this shows, that it's probably an issue with the upstream buildsystem. I have attached a cross-compilation output from AMD64 GNU/Linux to AArch64 Android. (Hopefully it shows up) 

~lattis REPORTED CLOSED 3 months ago