Open ChAoSUnItY opened 3 months ago
Can you check CR LF, LF and CR line break characters?
Yes, this is caused by setting of git which defaults line break characters to CR LF.
Maybe we can attempt to detect files' line break character and give proper warning message in the MAKEFILE?
Yes, this is caused by setting of git which defaults line break characters to CR LF. Maybe we can attempt to detect files' line break character and give proper warning message in the MAKEFILE?
For bootstrapping, stage0 is initially compiled with a standard compiler to generate a native executable. This compiler can then function as a cross-compiler, regardless of the operating system or computer architecture. It would be great if we can deal with CR/LF issue, allowing more toolchains such as MinGW-w64.
In the latest commit (cb34939), after using command
make distclean config ARCH=arm
then executesmake
to bootstrap, the process panicks about the corruptedlibc.inc
generated bytools/inliner.c
. The generated corruptedlibc.inc
could be seen here.Here's the sneak peek of the corrupted
libc.inc
, notice that this corruption is caused due to unmatched string double quotation mark:I can only reproduce this result on current laptop's WSL2 but on previous desktop's WSL2.