This bug was fixed in the package gcc-12 - 12-20220428-1ubuntu1
---
gcc-12 (12-20220428-1ubuntu1) kinetic; urgency=medium
* New upstream snapshot, taken from the gcc-12 branch.
gcc-12 (12-20220428-1) unstable; urgency=medium
* New upstream snapshot, taken from the gcc-12 branch.
Thank you Matthias!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-protection should only be enabled where it can work
To manage notifications about this bug go to:
htt
This bug was fixed in the package gcc-11 - 11.2.0-19ubuntu1
---
gcc-11 (11.2.0-19ubuntu1) jammy; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-11 (11.2.0-19) unstable; urgency=medium
* Update to git 20220324 from the gcc-11 branch.
This bug was fixed in the package gcc-10 - 10.3.0-15ubuntu1
---
gcc-10 (10.3.0-15ubuntu1) jammy; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-10 (10.3.0-15) unstable; urgency=medium
* Update to git 20220324 from the gcc-10 branch.
** Also affects: gcc-12 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gcc-10 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-10 (Ubuntu)
Status: New => Fix Committed
** Changed in: gcc-11 (Ubuntu)
Status: New => Fix Committed
** Chan
Re-ping again, this is breaking all (well there aren't too many) 486
compiles.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-protection should only be enabled where it
Re-ping for gcc maintainers,
could we please have the default "fcf-protection" be not applied to
`-march=i486 -m16` ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-pro
This bug was fixed in the package qemu - 1:6.0+dfsg-2expubuntu1
---
qemu (1:6.0+dfsg-2expubuntu1) impish; urgency=medium
* Merge with Debian experimental, remaining changes:
- qemu-kvm to systemd unit
- d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm,
The build in a PPA is now complete on all architectures, after some more
testing I'll upload that to Impish to avoid the issue on qemu's side
until fixed in the toolchain.
** Changed in: qemu (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/407156
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/407157
--
You received this bug notification because you are a member of Ubuntu
Bug
FYI - qemu interim fix LGTM in test builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-protection should only be enabled where it can work
To manage notifications a
Amurray was so kind to point out that we already do not use it on -m32
/* Enable code instrumentation of control-flow transfers.
Available on x86 and x86_64. */
#ifndef CF_PROTECTION_SPEC
# ifdef DIST_DEFAULT_CF_PROTECTION
# define CF_PROTECTION_SPEC "
%{!m32:%{!fcf-protection*:%{!fno-cf-pro
Broken in PPA or sbuild builds with 11.2.0-1ubuntu3
Last working case with 11.1.0-3ubuntu1
I'm not entirely sure of all the moving pieces here, but if true it
might be a late change causing some more FTFBFSes that might be worth to
fix in a single place at the toolchain before impish is complete.
13 matches
Mail list logo
