Package: gcc-12-aarch64-linux-gnu
Version: 12.2.0-14cross1
Severity: normal
X-Debbugs-Cc: deb...@flamingcow.io
When attempting to install gcc-12-aarch64-linux-gnu:amd64 on an arm64
system, conflicts prevent installation. I realize this is a silly thing
to want to do; this is attempt to simplify a
I forgot: the steps to reproduce are these
git clone https://github.com/darktable-org/darktable.git
git submodule update
cd darktable
./build.sh --prefix /usr/local --build-type Release
but of course, one needs the darktable dependencies before --
apt-get build-dep darktable
J.
Processing commands for cont...@bugs.debian.org:
> retitle 1038603 gcc-12 was compiled with BMI instructions, which seems to
> sometimes make it crash in older CPUs
Bug #1038603 [gcc-12] gcc-12 was compiled with BMI instructions, which seems to
it sometimes crashing in older CPUs
Changed Bug tit
Package: gcc-12
Version: 12.3.0-4
Severity: important
Dear Maintainer,
It seems that the Debian package of GCC 12 was compiled with BMI1 (and
BMI2) instructions (perhaps the wrong -march setting is being
used?). At least apparently (see below). Those are relatively new
instruction sets, and are n
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 18 Jun 2023 11:31:37 +0200
Source: binutils-bpf
Architecture: source
Version: 11
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Ma
binutils-bpf_11_source.changes uploaded successfully to localhost
along with the files:
binutils-bpf_11.dsc
binutils-bpf_11.tar.xz
binutils-bpf_11_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing control commands:
> severity -1 important
Bug #1032165 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Severity set to 'important' from 'serious'
--
1032165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032165
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: severity -1 important
updating the Built-Using tag almost always means, that you build against a new
compiler version, also most likely modifying all the target binaries
(lib*-cross-*), which are packaged as binary-independent packages. So a binNMU
just doesn't make sense for the -cro
8 matches
Mail list logo