This update has been unpushed.
This update has been unpushed.
I was able to build KiCad with this version of gcc12.
Understood. KiCad explicitly selects -std=gnu++17 in its cmake configuration, so it shouldn't be affected by a change to -std=gnu++23 as the default.
That is excellent news, Jakub. Thanks!
I'll run a test build and comment on the gcc-12.0.1-0.2.fc36 page.
It would be great if PR libstdc++/104099 could also be picked up, as that one is causing a build failure of KiCad in Rawhide as shown here:
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/3196619/
Still works with KiCad scripting console.
This fixes a problem with KiCad whereby the python scripting console would fail to open. Thanks very much for the fix!
Fair enough, regarding libheif. But I just tried again with "dnf update --refresh" and got errors on packages that appear to be part of Fedora itself. @fschwarz, so I get it right next time, are the errors below sufficient to justify the negative karma?
============================================================================================
Package Architecture Version Repository Size
============================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
libjxl x86_64 0.6.1-6.fc35 updates-archive 969 k
libjxl x86_64 0.6.1-6.fc35 updates 969 k
Skipping packages with broken dependencies:
gimp-jxl-plugin x86_64 0.6.1-6.fc35 updates 31 k
jxl-pixbuf-loader x86_64 0.6.1-6.fc35 updates 54 k
libaom x86_64 3.2.0-2.fc35 updates-archive 1.6 M
As @rathann indicated, this is not installable. Using:
dnf update --refresh --best --allowerasing
I get:
Error:
Problem: cannot install the best update candidate for package libheif-1.12.0-2.fc35.x86_64
- problem with installed package libheif-1.12.0-2.fc35.x86_64
- package libheif-1.12.0-2.fc35.x86_64 requires libjxl.so.0()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package libjxl-0.5-3.fc35.x86_64
- cannot install both libjxl-0.6.1-6.fc35.x86_64 and libjxl-0.5-3.fc35.x86_64
Confirmed fixed the bug. Thanks!
I was not able to trigger the bug after a half dozen logout/login to the same user. However, I do notice that thee are a lot of geoclue processes that are not cleaned up:
fedora33# ps -fe | grep sfalco
sfalco 911 1 0 11:11 ? 00:00:00 /usr/lib/systemd/systemd --user
sfalco 912 911 0 11:11 ? 00:00:00 (sd-pam)
sfalco 1130 1 0 11:11 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 1749 1 0 11:12 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 2357 1 0 11:13 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 2966 1 0 11:13 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 3560 1 0 11:14 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 4187 1 0 11:15 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 4794 1 0 11:16 ? 00:00:00 /usr/libexec/geoclue-2.0/demos/agent
sfalco 5228 911 0 11:17 ? 00:00:00 /usr/bin/dbus-broker-launch --scope user
sfalco 5229 5228 0 11:17 ? 00:00:00 dbus-broker --log 4 --controller 11 --machine-id 453c53fe1e0e40538136bd60780043d7 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000
I was able to build KiCad for aarch64.
Works fine. Thanks for the rapid fix.
I tried merging bcm283x-firmware-20200306-1.163d84c.fc32.aarch64.rpm into several images:
Fedora-Workstation-32-20200225.n.0.aarch64.raw.xz Fedora-Workstation-32-20200307.n.0.aarch64.raw.xz Fedora-Workstation-32-20200308.n.0.aarch64.raw.xz
In all cases, the dracut shell bug is still present.
Works properly. Thanks!
As per https://www.cqrlog.com/comment/7947#comment-7947 it looks like there is a significant bug in cqrlog-2.4.0, and upstream has recommended rebuilding with the tip of the source tree rather than with cqrlog-2.4.0.tar.gz.
As per https://www.cqrlog.com/comment/7947#comment-7947 it looks like there is a significant bug in cqrlog-2.4.0, and upstream has recommended rebuilding with the tip of the source tree rather than with cqrlog-2.4.0.tar.gz.
This update has been unpushed.