Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The linux arm32 compiler does not properly handle utf8-bom encoded inc files #710

Open
winddriver opened this issue Oct 8, 2024 · 2 comments

Comments

@winddriver
Copy link

The compilation environment is windows 10 x64, and the execution file of linux arm32 is generated by cross-compilation

Both fpc and lazarus are the latest versions pulled from gitlab

When an inc file is encoded with utf8-bom, including the file with $I will cause garbled characters

This is a demo project.
HelloWorld(inc_utf8_bom).zip

This is a screenshot of the run, in which two Chinese characters have become garbled.
image

If you use utf8 encoding, there will be no problem.
This is a demonstration project using utf8 encoding
HelloWorld(inc_utf8).zip

This is a screenshot of the operation. You can see that the Chinese is displayed normally.
image

@winddriver
Copy link
Author

Add a point, linux arm64 does not have this problem, so I suspect that linux arm32's cross-compile tool chain caused the problem, can you update the cross-compile tool

@LongDirtyAnimAlf
Copy link
Owner

The problem is the lack of GNU binutils for Android.
Recent Android tools are based on clang and llvm. FPC cannot use these newer tools. So we are stuck with the old ones.
You might try to find newer GNU tools (binutils) yourselves and point me towards them, in case I have missed them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants