-
Notifications
You must be signed in to change notification settings - Fork 27
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
undefined reference to 'memset' on macOS/arm64 #4
Comments
I managed to find an answer that seems to have at least gotten me through compiling. https://forums.raspberrypi.com/viewtopic.php?t=84506:
I put this in under my changes to LDFLAGS and the compiling completed without complaint.
I'll work on a PR. |
Hi and thank you. This is really strange. I will make some tests when I find some time. There must be a better solution, I hope. |
I'll note here additionally that the flag makes compiling work, but the code doesn't actually run. I'm not entirely sure why - I'll continue to explore. |
I think that's because of the rv32imac flag. The ch32v003 doesn't actually support this instruction set. |
Ahh yes, that makes sense. I'm compiling for the wrong thing. I am unfortunately back to unsuccessfully compiling on Apple Silicon/arm64.
I think it's clearly a linker issue, though I'm not really sure how to resolve it. |
I have no idea at the moment ;-( |
Did you perhaps use a different linker script or include other libraries? I don't know where the .text.startup.main comes from. |
Not too sure if it is still an issue with aaroneiche You can see the changes on Line 47 @ makefile Hope it helps. 😃 |
I'm not sure if its worth reopening issue #1 or just starting a new one, I'm running into a similar build error trying to build on an M1 MBP running Ventura (macOS 13.6.7)
I added the following to the makefile to fix an environment compiling error:
But otherwise the makefile is as it was.
I haven't been able to figure out a fix other than what's already addressed in issue #1. (and that's in the makefile already, obvious)
The text was updated successfully, but these errors were encountered: