Bug#1091769: oaklisp: loong patch test fail

2025-01-12 Thread Barak A. Pearlmutter
Well, it's in the configure.ac script already so I'll just leave in there and maybe someday it will work.

Bug#1091769: oaklisp: loong patch test fail

2025-01-09 Thread wuruilong
Hi, I'm very sorry, Oaklisp has not been verified locally, and currently GCC does not support it. I was very impatient to submit this bug, and I think it's better to close this bug now. It's safer to submit the corresponding patch after the local compilation is successful in the future. wuru

Bug#1091769: oaklisp: loong patch test fail

2025-01-06 Thread wuruilong
Hi, The current repository version of gcc does not support this option yet. Oaklisp needs to wait for gcc to be upgraded to support it. wuruilong On Mon, 6 Jan 2025 09:30:14 + "Barak A. Pearlmutter" wrote: > Xiao Sheng, > > Thanks for testing that -mabi=ilp32f patch. > > ---

Bug#1091769: oaklisp: loong patch test fail

2025-01-06 Thread Barak A. Pearlmutter
Xiao Sheng, Thanks for testing that -mabi=ilp32f patch. wuruilong (and other loong folks), Here is what the build log says: > configure:5169: gcc -o conftest ... -mabi=ilp32f ... conftest.c ... > gcc: error: unrecognized argument in option '-mabi=ilp32f' > gcc: note: valid arg

Bug#1091769: oaklisp: loong patch test fail

2025-01-06 Thread 肖盛文
Hi, I just test your patch[1] for loong64, it failed: The error log is: checking build system type... loongarch64-unknown-linux-gnu checking host system type... loongarch64-unknown-linux-gnu configure: WARNING: non 32-bit pointer platform detected configure: trying to enable 32-bit memory mode