Like Ma
Like Ma
> Don’t force push, makes it harder to review, use nullptr instead of 0 OK. Shall I combine two commits into one after reviewed so that keep one issue per...
But `name.c` depends on `libgc.a` . Does it need to be built manually?
Will the V dev team plan to support this kind of cross-build scenario?
> @ylluminate From what I understand, `ppc64le` is substantially different from `ppc` and `ppc64` on Darwin, but I am interested in the topic. Thank you for tagging me. Yes, `ppc64le`...
Not only `ppc64le`, but also `loongarch64` cross-compile need to be supported. I suggest something is similar with CMake toolchain file: ``` set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR ppc64le) set(CMAKE_C_COMPILER powerpc64le-rhel7-linux-gnu-gcc) set(CMAKE_CXX_COMPILER powerpc64le-rhel7-linux-gnu-g++) ```
> @likema By the way, why cross, why not build natively? For saving cost
> By the way, I am interested to implement `ppc64` support, if it is lacking. Primarily for BE, but LE should be easier in fact. Thanks. I also have `powerpc64-rhel6-linux-gnu-gcc`...