On 2/14/25 15:17, Matthias Klose wrote:
Control: tags -1 + moreinfo
On 13.02.25 21:41, Mo Zhou wrote:
Control: reopen -1
The problem persists, and the buildd is still failing on it several
hours ago:
still unable to reproduce with
g++ -c -std=gnu++17 -g -gsplit-dwarf -O3 -fopenmp -fPIC
-f
On 13.02.25 21:41, Mo Zhou wrote:
Control: reopen -1
The problem persists, and the buildd is still failing on it several
hours ago:
https://buildd.debian.org/status/fetch.php?
pkg=pytorch&arch=arm64&ver=2.6.0%2Bdfsg-1%7Eexp1&stamp=1739418834&raw=0
This is a regression. Setting CC=gcc-13 and
Processing control commands:
> tags -1 + moreinfo
Bug #1094828 [g++-14] g++ internal compiler error on arm64 when compiling
pytorch
Ignoring request to alter tags of bug #1094828 to the same tags previously set
--
1094828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094828
Debian Bug Tra
Control: tags -1 + moreinfo
On 13.02.25 21:41, Mo Zhou wrote:
Control: reopen -1
The problem persists, and the buildd is still failing on it several
hours ago:
still unable to reproduce with
g++ -c -std=gnu++17 -g -gsplit-dwarf -O3 -fopenmp -fPIC
-fstack-protector-strong -fstack-clash-prot
Source: gcc-15
Version: 15-20250208-1 (experimental)
Severity: normal
Dear Maintainer,
The following warning occurs in most c++ compilations and it will
cause many testsuite fails:
In file included from /<>/src/libstdc++-v3/libsupc++/cxxabi.h:51,
from ../../../../src/libstdc++-v
Hi Matthias,
On Fri, Feb 14, 2025 at 04:26:02PM +0100, Matthias Klose wrote:
> I don't want to apply this patch for trixie. Having these as and ld
> symlinks in the gcc_lib_dir had other issues. The main reason for that
Fair enough. However, we need some mechanism to redirect gcc into using
the
On 14.02.25 10:52, Helmut Grohne wrote:
Control: retitle -1 gcc-VER-TRIPLET may use binutils for a different
architecture
Control: severity -1 important
Control: tags -1 = confirmed patch
On Thu, Oct 03, 2024 at 12:40:53PM +0200, Erez wrote:
Just update my trixie container.
builder@5ba2a4b665
Yes, you are right.
Removing gcc-14-aarch64-linux-gnu:arm64 does solve the problem.
It was installed by dependencies.
I am using multiple architectures for cross compilation.
My real question is why do we have gcc-14-aarch64-linux-gnu:arm64 in the
pool?
Cross compilers using the same host and tar
Control: retitle -1 gcc-VER-TRIPLET may use binutils for a different
architecture
Control: severity -1 important
Control: tags -1 = confirmed patch
On Thu, Oct 03, 2024 at 12:40:53PM +0200, Erez wrote:
> Just update my trixie container.
>
> builder@5ba2a4b665d9:~$ cat /etc/debian_version
> trixi
Processing control commands:
> retitle -1 gcc-VER-TRIPLET may use binutils for a different architecture
Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross
compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"
Changed Bug title to 'gcc-VER-TRIPLET may
Processing commands for cont...@bugs.debian.org:
> forwarded 1092866 https://gcc.gnu.org/PR114065
Bug #1092866 [src:gcc-15] gnat-15 20250112 ftbfs on armel/armhf
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR114065'.
> severity 1092866 important
Bug #1092866 [src:gcc-15] gnat-15 20250112
11 matches
Mail list logo
