[Slackbuilds-users] [qemu-static] update-binfmts --import — intended manual step?

Lockywolf Laptop lockywolf at lockywolf.net
Sat Jul 11 12:46:50 UTC 2026


Julian Grinblat <julian at dotcore.co.il> writes:

> patch below, which I think will be useful for newcomers:

You can see the merge progress at the link below:

https://gitlab.com/SlackBuilds.org/slackbuilds/-/merge_requests/977

> As an aside, not part of this patch: I hit a build failure worth
> flagging if you're aware of it - the bundled static glibc fails with
> `OPEN_TREE_CLONE redefined [-Werror]` when built against the
> experimental linux-7.1.x testing kernel line (kernel-headers-7.1.x)
> rather than mainline -current. kernel-headers-7.1.x reformats some
> mount.h flags to bit-shift notation, which collides with glibc's own
> bundled definition of the same constant - harmless (same value), but
> fatal since glibc's build enables -Werror. Slackware's own official
> glibc build doesn't hit this, since it's built against mainline
> kernel-headers, not the testing branch. --disable-werror on the
> bundled glibc's configure works around it, in case it's useful to know
> about even without a formal patch.

I am afraid it's not really worth fixing at the moment, because kernel,
glibc, qemu, everything might change by the time 7.1.x gets into
-current, so rather than patching the existing version it might be worth
updating the glibc instead.

I think Ponce might be interested in knowing this, though, he has his
own branch dedicated to -current (see
https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page507.html)
But I suspect he will also say "when 7.1.x (or even something newer)
gets into -current."

-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)


More information about the SlackBuilds-users mailing list