Build errors, likely C23 related

Development
1

I haven’t pulled/built in a while, but tried today after doing some dirtyJTAG testing. I believe they’re related to the C23/Code Quality updates, because the first error is on constexpr. I haven’t started digging into the build system and CMake files yet, but am I just missing something stupid?

I just went back and checked out 869c7c0 Prepare to enable stronger build warnings and was able to build and carry on. I didn’t do any bisecting, that just looked like a good place to go in a hurry.

Thanks much!

1 Like
2

You’ll need to update to arm gcc 13+ or 14. That could be the issue.

2 Likes
3

That’s where I was just looking. Ugh, Ubuntu; I’m on 22.04 for reasons. Maybe I’ll just set up a VM with Ubuntu 24 for building :woman_shrugging:

Yup, grr.

┌──(matty💊s76)-[~/data/projects/BusPirate5-firmware/build_rp2040]
└─$ /usr/bin/arm-none-eabi-gcc --version
arm-none-eabi-gcc (15:10.3-2021.07-4) 10.3.1 20210621 (release)
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
2 Likes
4

We run 22.04 on the build server with arm GCC 13. I installed it manually, but it seems to work.

1 Like
5

I’m afraid to force gcc 13 and screw up other things.

I might actually upgrade my daily driver to Ubuntu 24 next week. Could be a good time to do it. If I have to mess with it, might as well go big! :rofl:

1 Like
6

Would be a wonderful middle ground between full VM to have an os virtual environment like Python has done. Installing all the specific versions of libraries per app (environment) instead of per OS.

Then again, node npm and php composer do the same and I absolutely hate how it’s implemented. I guess be careful what you wish for because it might monkey paw ya.

7

100%. I’ve been dreading/looking for an excuse to upgrade, so this might be it. After tomorrow, I’ll be between projects, so impact won’t be quite so bad.

1 Like