klasyc

Hello, I am facing the same problem, the error message is exactly the same as above. What I am trying to achieve is to compile mono as AOT cross-compiler (I...

Thank you for suggestion, @lambdageek! Now I am trying to use the `offsets-tool`, but it fails and I cannot find any documentation. That's pity because I am not sure what...

After some additional digging I managed to compile the offsets file, but at its beginning it contains `#ifndef HAVE_BOEHM_GC` macro which prevents my offset definitions from being used. My current...

Disabling of boehm helped, but now I have another compile error which seems to be related to the offset file: ``` | decompose.c: In function ‘mono_decompose_vtype_opts’: | ../../mono/metadata/abi-details.h:56:42: error: ‘MONO_OFFSET_MonoErrorExternal_init’...

So the AOT cross-compiler seemed to work, but it generates different binaries than the native ARM compiler :( The compiled binaries have even different size. In order to troubleshoot the...

After further analysis of the configuration process, I found an important difference: The cross-compiler's configure script prints: ``` checking which FPU to use... VFP checking which ARM version to use......

The most important assembly difference is in the main method: Native: ``` mono_aot_AotHelloWorld_plt: .local plt_System_Console_WriteLine_string .type plt_System_Console_WriteLine_string,#function plt_System_Console_WriteLine_string: .Lp_1: .byte 0,192,159,229,12,240,159,231 .long mono_aot_AotHelloWorld_got - . + 104,57 .size plt_System_Console_WriteLine_string,.-plt_System_Console_WriteLine_string .size...

I had to remove: - Type check at `lib/WebDAV/BasicAuthBackend.php` line 75 (already mentioned above). - Return type at `lib/Provider/OpenIDConnectClient.php::getTokenProfile()`. - Type of the first parameter of the `lib/Service/LoginService.php::login()` function. -...

Hi, I re-created the docker container and applied your patch. Basic authorization works fine, but bearer token does not work - I always get error 401.

No, it does not help. Perhaps there is some issue in the token validation...