Issues building Out-of-tree Driver Modules

infinitymdm

Hi folks,

I've been using an open source community driver called xone to use my Xbox Wireless dongle with my Xbox controllers. I recently got the kernel upgrade to 5.15. Naturally, that means I have to rebuild the driver against the new kernel. However, when I went to do so yesterday, I got some errors:

cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so

The package.yml can be viewed on my github. The errors here occur during the make command in the build step.

I suspect this issue is also related to the WIP toolchain rebuilds. Specifically, I believe the issue is that I'm using a newer version of gcc than the one that my kernel was built against. Not 100% sure about this though.

Is there some workaround I can use for now to build xone and use my hardware?

Staudey

Yeah, that's due to the toolchain update that is currently going on (or rather the rebuilds are still going on). You can either wait for the kernel to get updated, or (somewhat riskier), rebuild it yourself in the meatime.

infinitymdm

Staudey I actually already rebuilt the kernel myself against the new gcc. I had zero issues - it installed and worked just fine after a reboot - but since solbuild is sandboxed, it pulls linux-current and -headers from the official repo anyways. Do you know of a way to force solbuild to use my kernel instead?

Harvey

Seeing it is for local use and I assume you are on the stable repository or are on unstable but haven't updated since the sync earlier in the week: Build it against stable instead, from memory you need to do this:

Create the solbuild stable base image.
sudo solbuild init main-x86_64

To build a package against stable instead of running make use:
make build-stable

infinitymdm

Harvey I'm actually on unstable (it would be a shame if I didn't test my own packages 😄 ) so unfortunately this won't work for me. Is there some other workaround I can use? If I could just tell solbuild to use my kernel package instead of the one from the repos, I imagine that would do the trick.

Harvey

There is the possibility of a local repo. https://getsol.us/articles/packaging/local-repository/en/ which is how we build things against build deps not yet in the repository. But in this case it is not really practical there is just shy of 1,000 package rebuilds in progress so it would be more than just the kernel you needed. Basically in this scenario, do not do this.

If you have not updated since we performed a sync on 2022-03-22T17:12:56+01:00 then building against stable will probably still work. If you have updated after you could try rolling back updates to before this change https://getsol.us/articles/package-management/history-and-rollback/en/ reboot and build against stable.

As always make sure you have a backup.

infinitymdm

Harvey

If you have not updated since we performed a sync on 2022-03-22T17:12:56+01:00 then building against stable will probably still work.

This did the trick, even though I had updated since the previous sync. I had previously set up a local repo for another project, but make local failed with the same gcc errors. make build-stable worked for me. Thanks!