You are not logged in.

#1 2022-03-12 01:55:26

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

[SOLVED] 5.16.12 dkms modules not building

Before the linux update to 5.16.12, I had to hold gcc at version 11.1 because the 5.16.8 kernel was built with gcc 11.1 and my dkms modules wouldn;t build. I've now updated linux to 5.16.12 and updated gcc to 11.2 (with gcc 11.1 and linux 5.16.12, I was getting the same incompatible compiler error). Now I'm seeing the following error:

make -C /usr/lib/modules/5.16.12-arch1-1.0/build M=/var/lib/dkms/uvesafb/1.0.4/build/src modules
make[2]: Entering directory '/usr/lib/modules/5.16.12-arch1-1.0/build'
  CC [M]  /var/lib/dkms/uvesafb/1.0.4/build/src/uvesafb.o
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
make[3]: *** [scripts/Makefile.build:287: /var/lib/dkms/uvesafb/1.0.4/build/src/uvesafb.o] Error 1
make[2]: *** [Makefile:1846: /var/lib/dkms/uvesafb/1.0.4/build/src] Error 2
make[2]: Leaving directory '/usr/lib/modules/5.16.12-arch1-1.0/build'

Apparently there's an issue with the gcc-plugins versions, specifically structleak_plugin.so. I have 3 dkms modules I need and all 3 fail their build in the same way.

Any insights? Another fix needed?

Last edited by jghodd (2022-06-29 19:18:56)

Offline

#2 2022-03-12 05:05:08

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED] 5.16.12 dkms modules not building

Yes, I'd agree, looks a plugin error, specifically structleak_plugin.so. I might hope that a rebuild of gcc-plugins isn't too difficult for the build servers or the maintainers, but it would be forward of me to assume so.  But I think that's what's required.

Last edited by levi (2022-03-12 05:05:46)


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#3 2022-03-12 08:26:31

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

I'm not sure the solution is as simple as a rebuild, but I can try that sometime later today. gcc-plugins are(is) distributed as part of the linux-headers package, btw. I assume linux and linux-headers were both built and packaged at about the same time. it may require a deeper look.

Last edited by jghodd (2022-03-12 08:27:21)

Offline

#4 2022-03-12 20:30:41

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED] 5.16.12 dkms modules not building

I was suggesting waiting for a rebuild by the arch32 build team of the package containing gcc-plugins, which I assume you're right to specify as linux-headers.  linux-headers has the same versioning string as the kernel, so I would assume it was built about the same time, but there's always the possibility that part of it either wasn't rebuilt for some reason, or was rebuilt before the kernel was built.

But yeah, the flexibility of arch linux in general means if you can get the PKGBUILD for linux-headers you might well be able to build it yourself.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#5 2022-03-13 00:40:39

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

Well, the linux-headers package is created when building the linux package - which I'm about 5 hours into right now - so both packages were actually built together. That's why I'm not convinced that a rebuild will fix it. But it is worth a try. Took a minute to figure out how to do non-aur arch32 package builds, but it seems to be rolling along just fine. I'll post here when the build's done and I can test it.

Offline

#6 2022-03-13 08:05:41

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

Ok. So apparently a rebuild does fix the problem. My dkms modules are now building as expected. No errors. I'm rebuilding linux again now with a 1.1 release number to differentiate it from the core repository's release 1.0. I am aware that linux-5.16.13 is currently in the build queue, but has not entered either the staging or testing repositories.

As far as I've been able to tell, to build a non-aur arch32 package, one concatenates the upstream PKGBUILD with the arch32 PKGBUILD and uses the source files (patches and in this case, config files) from both. The makepkg run against the frankenstein'ed PKGBUILD did correctly select the config.i686 config file, so I'm assuming I got it working as it should. If I've missed a step, please let me know.

I've not yet booted/rebooted to the rebuilt kernel and won't until this re-rebuild is done (although I was running linux 5.16.12 and am still running 5.16.12). I'll post here after testing it in the morning.

Cheers

Offline

#7 2022-03-13 19:01:06

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

Thumbs-up on the rebuild. Seems to have fixed the problem.

Cheers

Offline

#8 2022-03-13 22:58:17

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED] 5.16.12 dkms modules not building

Now we just have to wait for the package to arrive for anyone else who might discover this problem.  But that said you don't actually need linux-headers to build user software, so the number of people building kernel modules for this old software is kind of limited I would hope.  So perhaps as long as you've got a way to work around this problem is good enough, I'm not sure.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#9 2022-03-31 19:32:25

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

And it's back with 5.16.15. This is a pretty significant issue. Modules are unbuildable and we shouldn;t have to rebuild the kernel every time y'all release a new version! This needs to be solved at the build/release level, not by individual users.

The error "cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so" suggests kernel builds are being made against a library, or libraries, that haven't been released yet. I saw the same issue with boost, which was build against python 3.10, which hasn;t been released yet. These builds shouldn;t be done against unreleased software versions!

Offline

#10 2022-04-01 07:46:24

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

Which DKMS package are you compiling? Can you give me a pointer to the AUR?
Are you on i686 or pentium4 (subarchitecture)?
Are you on stable or testing repos (or a mixture)?
Ah, and 5.17.1 is coming up anyway at the moment.. :-)

Offline

#11 2022-04-01 19:57:23

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

I'm using the uvesafb, r8101, and r8168 dkms modules, all 3 of which fail to compile - they're pretty standard. I'm on an i686 system using the stable repos with the following exceptions - go-1.17.2, mixxx-2.3.2, kdecoration-5.24.3. I had to downgrade boost-1.78 to v1.76, since 1.78 was built against python 3.10 which has not yet been released into the stable repository. The boost downgrade also meant a rebuild of libphonenumber, and was necessary to build calamares which has a heavy dependence on boost. So, I'm not seeing anything there that should interfere with the building of kernel modules, but I am seeing more than enough evidence that packages are being built against test or staging software and then released to the stable repository. This isn;t my first rodeo where arch32 is concerned. This type of issue comes up time and time again. I'm constantly having to rebuild, downgrade and plunder packages from the test repos to get a functioning system and a functioning build for my users.

And yes, I know 5.17 is in the works, but will it really solve this issue? arch64 had no issues with 5.16.x where dkms modules were concerned, and I just finished building 5.16.16 which works just fine having been built against a stable system, even though your own build of the same version failed to compile any of the dkms modules when installed. Y'all are missing something...

Last edited by jghodd (2022-04-01 20:04:19)

Offline

#12 2022-04-01 23:10:39

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED] 5.16.12 dkms modules not building

Perhaps this just requires that linux, linux-headers and gcc are all promoted from testing to stable as a block.  But I've never built a dkms module, so my only experience comes from this thread really.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#13 2022-04-02 08:26:55

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

Well, the "rodeo" stems from the fact that basically two people are trying to keep things alive in spare time.
There is the buildmaster (the automatation system) handling the dependencies and pushing things from staging to testing, then to stable.
This sometimes goes wrong (or I force push something thus breaking dependencies). Ususally the problem is the software not rebuilding for 32-bit.
The other issue is that the user base of Arch32 is really thin, I really don't expect even one user per package
who could provide feedback whether the package is runnig.

Patches are always welcome. :-)

https://archlinux32.org/buildmaster/
This shows 7500 build issues (usually the size of the queue is a good indicator of how many build jobs
got stuck). Assuming an estimate of 30 minutes per problem to investigate this results in 156 person days!
Make your own calculations, how much man power you need to fix all issues.. :-)

Concerning DKMS: I'm personally not using a single module, so this explains, why I didn't test it in the past.

Offline

#14 2022-04-02 08:30:45

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

go dropped "below-SSE2 support" officially, if you like to do a fork of go, then you get a i686 version again.

Offline

#15 2022-04-02 08:34:35

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

uvesafb-dkms:

Cloning into bare repository '/data/work/arch32/uvesafb-dkms/uvesafb-dkms'...
fatal: remote error:
  The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improvin … ty-github/ for more information.

r8101-dkms
r8168-dkms

worked fine on pentium4.

The python 3.10 issue is a tricky one: many many packages didn't make the migration smootly from
python 3.9. I can force push all packages to version 3.10, but this will break a bunch of stuff for
3.9 (given the latest ffmpeg/ffmep4.4 issues, I don't feel conformable to push it). Now the problem
there is usually, that the dependency system doesn't record the python dependencies properly.
Especially tricky is when Python breaks build systems like meson - then we have a much bigger
problem not being able to build things depending on meson..

Offline

#16 2022-04-02 08:51:18

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

i686 stable works for me for
r8101-dkms
r8168-dkms
uvesafb-dkms (after fixing the git download links in source)

I have:
dkms 3.0.3-1.0
linux-headers 5.16.15.arch1-1.0
gcc 11.2.0-3.4
r8101-dkms 1.035.03-2
r8168-dkms 8.049.02-2
uvesafb-dkms 1.0.4-1

I can not reproduce your DKMS build issues, sorry. Something must be different..

Offline

#17 2022-04-02 18:51:20

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

@abaumann - i am very aware of the fact that there are only 2 of you keeping this going, and the amount of work it takes to keep everything straight. if i didn;t, my posts would fill your forum. but i don;t do that, and instead i take the time to find the right pieces from the testing repos, or build them as i need them. i even leave posts for my users that despite my grumblings over arch32, the job of maintaining it is being handled by only 2 people and it's an eye-wateringly huge job for 2 people.

i'll take a look at the uvesafb source and push a fix. since i have the source code locally, i didn;t notice the git change.

however, having to rebuild the kernel is a big enough pain in the butt to prompt a forum post. since you've been able to build the modules against your own system's kernel, i will take a look at everything i have installed in case i installed something into my own system from testing or staging that still may be ahead of where you're at in the stable repos. nothing comes to mind, but that doesn;t mean i haven;t forgotten something. pacman usually tells me what's out of sync and installed locally and the only thing it's telling me is that archiso is behind the current version.

however i do know exactly what makes it into my archiso builds (where uvesafb is a critical module to provide support for the intel gma500 family of graphics processors) and only the packages i listed are out of sync with the stable repos.

as for python, i wouldn;t want you to push 3.10 until it's ready. just please be careful what you're building against it right now. as i pointed out, you built boost against 3.10 and pushed it to the stable repository. boost should have been left at v1.76 with python 3.9 until 3.10 was ready to go. that's just one example. i also maintain a repository for my users that i need to keep updated and i run into version incompatibilities all the time. it's time consuming on my side to have to deal with that. it gets really bad when you're pushing a new version of kde/plasma/qt5 and the versions of everything are all over the board. but, i know there are only 2 of you maintaining things - i just do what i have to to solve the puzzle.

so, this is not so much a complaint than a wtf. the kernel installation should be able to build dynamic modules, otherwise it's missing a big part of its functionality.

I have:
dkms 3.0.3-1.0
linux-headers 5.16.15.arch1-1.1 (rebuild)
gcc 11.2.0-3.4
r8101-dkms 1.035.03-2.0
r8168-dkms 8.049.02-1
uvesafb-dkms 1.0.4-1

I should be able to do a pacman query to identify anything locally installed using 'pacman -U'.

as for go, i'll just rebuild when i need to.

Offline

#18 2022-04-02 23:24:09

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

i think we have a bigger issue here with boost, and perhaps other packages built against python-3.10. first, these packages all require boost:

alembic  boost  clucene  codeblocks  cpp-hocon  facter  glom  hugin  kig  kmymoney  leatherman  libappimage  libcmis  libetonyek  libixion
libkolabxml  libphonenumber  librevenge  librime  libtorrent-rasterbar  libwhereami  maeparser  mapnik  openimageio  openshadinglanguage  openvdb  python2-tagpy
scantailor-advanced  scribus  source-highlight

the surprise was that gdb also relies on boost-libs:

ldd /usr/bin/gdb
        linux-gate.so.1 (0xb7f06000)
        libreadline.so.8 => /usr/lib/libreadline.so.8 (0xb7541000)
        libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0xb74cc000)
        libdl.so.2 => /usr/lib/libdl.so.2 (0xb74c7000)
        libguile-2.2.so.1 => /usr/lib/libguile-2.2.so.1 (0xb737c000)
        libpython3.9.so.1.0 => /usr/lib/libpython3.9.so.1.0 (0xb6fc5000)
        libpthread.so.0 => /usr/lib/libpthread.so.0 (0xb6fc0000)
        libm.so.6 => /usr/lib/libm.so.6 (0xb6eb6000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb6e86000)
        liblzma.so.5 => /usr/lib/liblzma.so.5 (0xb6e59000)
        libmpfr.so.6 => /usr/lib/libmpfr.so.6 (0xb6d94000)
        libgmp.so.10 => /usr/lib/libgmp.so.10 (0xb6d08000)
        libsource-highlight.so.4 => /usr/lib/libsource-highlight.so.4 (0xb6c53000)
        libdebuginfod.so.1 => /usr/lib/libdebuginfod.so.1 (0xb6c4a000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6a2a000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb6a0b000)
        libc.so.6 => /usr/lib/libc.so.6 (0xb6812000)
        libgc.so.1 => /usr/lib/libgc.so.1 (0xb67bb000)
        libffi.so.8 => /usr/lib/libffi.so.8 (0xb67b0000)
        libunistring.so.2 => /usr/lib/libunistring.so.2 (0xb662d000)
        libltdl.so.7 => /usr/lib/libltdl.so.7 (0xb6621000)
        libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0xb65ea000)
        /lib/ld-linux.so.2 => /usr/lib/ld-linux.so.2 (0xb7f08000)
        libutil.so.1 => /usr/lib/libutil.so.1 (0xb65e3000)
        libboost_regex.so.1.78.0 => not found
        libcurl.so.4 => /usr/lib/libcurl.so.4 (0xb6533000)
        libnghttp2.so.14 => /usr/lib/libnghttp2.so.14 (0xb6504000)
        libidn2.so.0 => /usr/lib/libidn2.so.0 (0xb64e1000)
        libssh2.so.1 => /usr/lib/libssh2.so.1 (0xb6497000)
        libpsl.so.5 => /usr/lib/libpsl.so.5 (0xb6484000)
        libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0xb63f0000)
        libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0xb6178000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb611b000)
        libzstd.so.1 => /usr/lib/libzstd.so.1 (0xb6074000)
        libbrotlidec.so.1 => /usr/lib/libbrotlidec.so.1 (0xb6066000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb604c000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb5f66000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb5f33000)
        libcom_err.so.2 => /usr/lib/libcom_err.so.2 (0xb5f2e000)
        libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb5f1d000)
        libkeyutils.so.1 => /usr/lib/libkeyutils.so.1 (0xb5f15000)
        libresolv.so.2 => /usr/lib/libresolv.so.2 (0xb5f02000)
        libbrotlicommon.so.1 => /usr/lib/libbrotlicommon.so.1 (0xb5edf000)

note the reference to libboost_regex.so.1.78.0 in the middle of all that.

so, without python-3.10, boost and libboost 1.78 don't work and need to be downgraded to 1.76 with python-3.9. but without boost 1.78, a whole lot of software that's been pushed to stable doesn;t work. i think we're in a catch-22 here and i have no idea how many packages actually have a dependency on boost-1.78 - they're linked against 1.78 even though they don;t have an explicitly listed dependency (PKGBUILD depends=).

Last edited by jghodd (2022-04-02 23:27:53)

Offline

#19 2022-04-03 06:52:55

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

Your analysis of the situation is absolutely correct, this is exactly the problem.. :-)

What I usually do in this situation is to provide a shim package (icu67, llvm11-libs, etc.) which keeps parts linked against the old libraries around (same for boost, lllvm, etc.).
Then I can safely push things to stable. Then do the rebuilds. Some software, which cannot be rebuilt, will then stick to the shim packages, which deviates from
upstream, but, oh, well, it works. Some software like rust, firefox, thunderbird only work currently with the help of shim packages (and I don't think this will ever
change as rebuilding those beasts takes too much time and computing time, and they are convolated examples of software).

Adding the shim packages as depends is a good idea, but then I have to add it everywhere, just to remove them later on again, when rebuilding the software.
This causes a lot of unnecessary rebuilds. And it deviates from upstream, where those packages don't exist. So far I said, users can be notified in the announcements,
they should install shim packages. Currently there is a problem, as the rebuild process upstream is neither automatized nor fully transparent, so we actually
don't know what exactly has to be rebuilt in python 3.9 to 3.10. we rrely on the stream of updates from upstream. If one rebuild fails due to 32-bit issues, then
we notice that, but sometimes (too) late.

With python it's difficult: I thought about using python39 from the AUR, but then you have to build all python modules against 3.9 and 3.10. This creates a lot
of double packages, without some automatiation, this is not feasible.

We once discussed internally a method to test packages automatically better. I would like to have something like "install a package, run some --help or simple test".
If I encounter link issues or "Illegal Instruction" or so, I could raise an issue, flag the package or even trigger automatic rebuilds. The problem is: I have to test
this on real hardware, the issues don't always show up in virtual machines (with proper CPU emulation settings, as the emulation is not complete and leaks opcodes
of the host - for instance Intel branch cache deactivation) or it doesn't show up at all as in chroots. I cannot run old machines 24x7, as they would fast be close to
0x0 operation. :-)

Another issue is, that many authors now say SSE2 ist required and it is part of the minimal ISA for IA32. This makes errors on i686 and especially i484 more and more
hard to fix (configure and meson options disappear, whole working configure support get replaces with simple meson or cmake files). So now I have to read
and patch software everywhere to disable SSE2, this can be quite time consuming.

BTW: The buildmaster has a link "broken dependencies in the database": this shows all broken dependencies, so basically this is a global lddree...

Offline

#20 2022-04-03 07:11:46

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

There is another issue currently: haskell and nodejs stuff doesn't work since ages (and I don't think anybody still uses it but the rare call to a shellcheck or a pandoc).
So I would personally drop them, as they are unportable now (at least ArchlinuxARM never bothered to bootstrap for instance haskell for armv6, armv7, aarch64). The
only reason, it is in Arch32 is, it was there and working in Archlinux 32/64-pre-2017, so as long as it worked, why not keep it.

I tried to bootstrap haskel from older working versions but I ended up in things corrupting the stack or worse..

Those packages are always on error and polute the buildmaster.

Same could be said for i486, which is more an experimental toy of mine. There I have to make a huge blacklist, because
I cannot make thousands of packages work on ancient hardware.

I was also once considering just to ignore new software, as it is not likely to be portable and x86_64 anyway..

Offline

#21 2022-04-03 07:12:59

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

Sorry for the long posts, but I do value feedback of this kind and I like to explain things, as they (sadly) are. :-)

Offline

#22 2022-04-03 07:19:28

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

Ah, and for instance: https://bugs.archlinux32.org/index.php? … ask_id=245 makes me wonder, whether Python 3.10 works on IA32 at all..

Offline

#23 2022-04-03 07:54:14

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED] 5.16.12 dkms modules not building

I do have one haskell interpreter installed, although I haven't used it as I recall in about a year.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#24 2022-04-03 22:06:44

jghodd
Member
From: Jetersville, VA
Registered: 2019-07-14
Posts: 48

Re: [SOLVED] 5.16.12 dkms modules not building

@abaumann - i have no issue with long explanations, Andreas. was a software engineer for 30 years (until the 2008 recession and my age conspired to leave me unemployed for the past 11 years), so i do have a pretty good idea just how much work you 2 guys are doing, and i appreciate getting some details on the issues you're facing. i don't envy you, bud.

i do use the shims whenever i find i have to. the icu ones seem to crop up pretty often, but aren;t the only ones i occasionally have to use. as you described, though, i don;t see them being used effectively for the current issues. between the emerging assumption of sse2 support and the dance you have to do to release coherent packaging, you're obviously facing an enormous task.

for now i'll be patient and let my users know that they might want to hold onto whatever works for them right now until you're able to resolve things - whatever the resolution turns out to be. most of my users are running arch64 anyway.

i have no 32-bit hardware either, btw. i have a headless intel duo laptop running arch32 i use for building, and a VM i use for testing. i'd be happy to post any issues i come across, if that helps.

Offline

#25 2022-04-08 07:33:53

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: [SOLVED] 5.16.12 dkms modules not building

It is a challenging "hobby project", I would say. :-)

blender:

libpython3.10.so.1.0 => None

Now I have the same issue there. I might have to move now to Python 3.10 in stable, with all (the possibly nasty) consequences..

I'm always glad to get feedback, but there is no way I can run and test all software myself.

Offline

Board footer

Powered by FluxBB