You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
libgcc.a uses VFP register arguments, bin/cold.package.elf does not (hard-float upgrade fails) #769
Testing with kernel 4.2.0, vscode addon version 0.8.3 (released yesterday), GCC arm-none-eabi-gcc (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614 on macOS (M1 / Apple Silicon)
All of these versions * should * be correct, per #703 , but it's still failing to compile. Downgrading to kernel 4.1.2 (pros conduct upgrade kernel@4.1.2) compiles correctly, upgrading back to 4.2.0 fails again. I've also uninstalled/reinstalled the toolchain.
I don't know if you're still having the issue but I solved it on a similar setup (M4 Mac) by running a python virtualenv (either via conda or venv) so the python version is NOT 3.9.6-the Mac system version, and then building. Apparently there are some incompatibilities with the build process and that version of python, although I do not fully understand exactly what is going wrong. Please try activating a virtualenv (I used python 3.12) and then running pros make clean followed by pros make and let me know if that works for you too.
It would be pretty shocking if a python version change breaks pros make a little but not entirely... pros make (and pros make clean) just directly call make and, afaik, do nothing else
Activity
AndrewLuGit commentedon Apr 15, 2025
Try running
pros make cleanto delete the cold package, then see if it builds properlyapalrd commentedon Apr 16, 2025
Already did that as well.
ncodes16 commentedon Jul 8, 2025
I don't know if you're still having the issue but I solved it on a similar setup (M4 Mac) by running a python virtualenv (either via conda or venv) so the python version is NOT 3.9.6-the Mac system version, and then building. Apparently there are some incompatibilities with the build process and that version of python, although I do not fully understand exactly what is going wrong. Please try activating a virtualenv (I used python 3.12) and then running
pros make cleanfollowed bypros makeand let me know if that works for you too.djava commentedon Jul 8, 2025
It would be pretty shocking if a python version change breaks
pros makea little but not entirely...pros make(andpros make clean) just directly callmakeand, afaik, do nothing elsedjava commentedon Jul 8, 2025
well, theres a little more to it, but not a lot: https://github.com/purduesigbots/pros-cli/blob/1185b7d144fa54790ec7c86e85c51783371da91b/pros/conductor/project/__init__.py#L216