There are a lot of merge requests in the queue. I approved a few without
as much checking as I would like to do. I expect to do more of the same,
so git master may be unstable for a while.
We will have to do a lot of testing before the actual release.
For now, I've gotten side tracked on fi
Is there a way to catch configure time test code snippets that don't
compile? An example within our code would be great.
If so, I'm pretty sure I can move the test I need from run time to compile
time.
Has anybody actually tested our cross build mode? That is run on X86,
cross build for ar
Python 2 has been upstream EOL for 5 years. The burden here should be on
people who want to keep supporting it, not on people who want to drop
support for it.
On 2025-01-30 18:19, Fred Wright via devel wrote:
On Wed, 29 Jan 2025, Hal Murray wrote:
That makes sense. But I'm missing the next s
> On 01/31/2025 12:59 AM PST Hal Murray via devel wrote:
>
>
> Currently, our CI cross compile armhf case is failing. We discussed this
> back in Sept and I fixed things by handling each of 5 cases individually.
> It turns out there are more than 5 cases. I missed the others so that's
> why cros
Currently, our CI cross compile armhf case is failing. We discussed this
back in Sept and I fixed things by handling each of 5 cases individually.
It turns out there are more than 5 cases. I missed the others so that's
why cross armhf is currently failing.
I can add another handful of spec
