Add safety REVISION bump
After disabling pipewire, the PLIST had to be adjusted. When pipewire was
present, it was also built with the header. To be on the safe side, REVISION
bump after the PLIST update.
Pointer from phessler
Qt6WaylandClient and Qt6WaylandClient missing version sync
Qt6WaylandClient and Qt6WaylandClient moved from qtwayland to qtbase.
I forgot to move the versions. With this commit, they were also bumped and the
REVISION was increased.
Spotted by aja
cmake: fix build with Qt 6.10 (#100)
The 'Qt6FooPrivate' targets have been split into separate CMake files
in Qt 6.9, and require a 'find_package(Qt6FooPrivate)' call starting
with Qt 6.10.
See also: https://bugreports.qt.io/browse/QTBUG-87776
Update to Python 3.13.11, ok kmos (maintainer), sthen
3.13.10 was a rather massive update and .11 adds a few fixes on top,
some of them for not too terrible security issues:
https://www.python.org/downloads/release/python-31310/https://www.python.org/downloads/release/python-31311/
The annoying bit about this update is that our homegrown expat build
system does not install expat_config.h, which, strangely, is autoconf
results exposed in a public header (next to a few XML_ things). Until
that's sorted in base we get to patch the Python code since the expat
maintainer made the mitigation knobs only available behind some config
knobs, which the new Python code assumes to be enabled.
replace the cas spinlock in kernel mutexes with a "parking" lock.
this is motivated because cas based locks are unfair, meaning that
no effort is made by the algorithm to try and give CPUs access to
the critical section in the order that they tried to acquire them.
cas based locks can also generate a lot of work for the cache
subsystem on a computer because every cpu ends up hammering the
same cacheline.
the combination of these effects for heavily contended mutexes can
get some systems into a situation where they don't make progress,
and are effectively livelocked.
this parking mutex mitigates against these problems.
it's called parking because it was very heavily influnced by what's
described in https://webkit.org/blog/6161/locking-in-webkit/. the
big influence is that the lock itself only has to record it's state,
but the machinery for waiting for the lock is external to the lock.
[82 lines not shown]
PREFIX_ADJOUT_FLAG_DEAD is no longer needed and can be replaced with
a check that the attrs pointer is NULL. Refactor the code now a bit
since the logic got a bit simpler.
OK tb@
Extend ptrace(2) PT_GET_THREAD_* to include thread names.
Use a new define larger then _MAXCOMLEN to avoid that define from
propagating to ptrace.h. Ensure that pts_name is large enough with
a compile time assert.
okay claudio@ jca@
