-
Notifications
You must be signed in to change notification settings - Fork 54
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
Compilation failure under mingw64 #16
Comments
Some exploration later I get...
Then full configure and make runs out of memory (32G) - mem just keeps increasing until it's all used. It does actually build the tools and I can at least get sense out of -v / -h so they look functional. Problem appears to be that when it's building libraries mem use just keeps increasing. Trying non-multilib now |
I don't run Windows so I can't reproduce this easily. Are you using mingw or are you using gcc under WSL? I'm a little confused. I develop on Ubuntu, so you should find Ubuntu under WSL is the path of least resistance on Windows. The GCC build is notoriously kludgey. |
You could also try getting a prebuilt Windows RISC-V embedded toolchain like from here: https://www.embecosm.com/resources/tool-chain-downloads/#riscv-stable You'll just have to update the Makefiles to use the toolchain you chose. |
Yeah, aim is to get a good win10 native toolchain (which I imagine will be desirable) Been using msys/mingw but it seems a dead-end under Windows - it's compiled a load of stuff but has been sat doing nothing for about five hours
I've got several X86_64 Linux systems as well. Trying to work out how to do a cross-compile. Using Ubuntu I apt-got mingw64 which gave me a Linux version and sure enough ....
I just dunno how to get ./configure to use the mingw64 stuff instead of the linux versions (tried --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 but that just made linux elf output) If you can gimme a clue that'd be handy - if you're not overly conversant with cross compiling I do know people who can guide me in the right direction (although they're all highly PASCAL focused...) |
@peardox I've had pretty good success using WSL. (Windows Subsystem For Linux). I've not recently built for this particular project, but I suspect it would work. If you've not used it before, beware there are two flavors: WSL 1 and WSL 2, each with their own merits. |
@gojimmypi Yeah, I use WSL2 extensively as well as Linux and Windows (even a little Mac stuff). I use WSL to build things like (very slightly) custom debug probe etc. The thing is that Windows is the most popular OS so making Windows Pico friendly would be advantageous. I'm thinking specifically of things like learning Risc-V assembler ( and C/C++ I guess) on a device that costs a fiver. The present solutions are all way too techie for a newbie so I'm looking at a simple IDE that purely does Pico - hence the desire for good toolchains |
Just managed a gcc-13 Win64 build without multilib Now gonna try gcc-14 with multilib |
Some success (tada).... IMHO 64Gb MAY be required for a multilib build The output from a test shows the files to be....
Using mingw64 to 'help' with the toolchain ATM (provision of ninja + cmake) If anyone wants to try out the (very experimental) version it's at https://peardox.com/pico/gcc14-no-zcmp-no-multilib.zip |
Does a load of the easie bits then gets to GCC and eventually...
There is a gcc/libcpp/include/line-map.h in the gcc git however and it compiles under Linux OK - problematic MSYS toolchain???
The text was updated successfully, but these errors were encountered: