On 10/01/2025 12:47, Sylvestre Ledru wrote:
Le 10/01/2025 à 12:08, Emilio Pozuelo Monfort a écrit :
Sylvestre, can those be added back, so
that amdgcn-tools can move to a newer llvm?
Sure, do you know how to do that?
I don't think it was intentional
I don't know. I see this
Control: clone -1 -2
Control: reassign -2 src:llvm-toolchain-19
Control: retitle -2 llvm-toolchain-19: readd gcn targets
Control: block -1 with -2
Hi,
On Thu, 12 Dec 2024 12:05:59 +0100 Matthias Klose wrote:
On 12.12.24 00:07, Bastian Germann wrote:
> On Fri, 4 Oct 2024 18:50:41 +0200 Sylvestr
Source: gcc-6
Severity: serious
Nothing is using GCC 6 anymore, so we are removing it from testing. We
will ship buster with GCC 8 and most likely GCC 7. This bug is to prevent
GCC 6 from migrating back to testing.
Emilio
-- System Information:
Debian Release: buster/sid
APT prefers unstable
On 01/06/18 11:07, Matthias Klose wrote:
> On 01.06.2018 10:44, Emilio Pozuelo Monfort wrote:
>> Source: gcc-8
>> Version: 8.1.0-5
>> Severity: normal
>>
>> Hi,
>>
>> gcc-8 arch:all builds take up to 20h because they do a full build, only
>> to
Source: gcc-8
Version: 8.1.0-5
Severity: normal
Hi,
gcc-8 arch:all builds take up to 20h because they do a full build, only
to ship the arch-indep packages:
gcc-8-locales deb devel optional arch=all
gcc-8-source deb devel optional arch=all
libgccjit-8-doc deb doc optional arch=all
libstdc++-
On Sun, 2 Oct 2016 21:16:59 +0530 Pirate Praveen wrote:
> package: gccgo-6
> version: 6.2.0-5
> severity: serious
> justification: this is causing ftbfs on powrpc
>
> src/gitlab.com/gitlab-org/gitlab-workhorse/vendor/github.com/getsentry/raven-go/client.go:25:30:
> error: import file 'github.com/
On 03/08/16 19:37, Matthias Klose wrote:
> I'd like to make the GCC 6 defaults change later this week(end), including icu
> 57 and boost 1.61 transitions.
>
> While the bug number of the GCC 6 related issues is still high, I'm proposing
> to
> fix these on the fly (as suggested/discussed with Nil
Package: libgnatprj6
Version: 6.1.1-6
Severity: serious
A few days ago, libgnatprj6 was working just fine. However it looks like
one of the recent uploads has broken it, causing undefined references:
https://buildd.debian.org/status/logs.php?pkg=asis&ver=2015-1%2Bb1
https://buildd.debian.org/stat
On Wed, 16 Dec 2015 16:57:52 +0100 Mattias Ellert
wrote:
> tis 2015-11-10 klockan 15:50 +0100 skrev Aurelien Jarno:
> >Â
> > Bug submitted upstream as PR68273.
>
> Hi!
>
> How should I handle this? Will there be a solution to the gcc bug
> within a not too distant future, or is this likely to r
On Tue, 02 Jun 2015 08:30:54 +0200 Roberto Bagnara wrote:
> On 06/02/15 08:12, David Bremner wrote:
> > Source: ppl
> > Version: 1:1.1-3
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the
> > past)
> >
> > In an up to date sid chroot, ppl compilati
On 21/09/14 02:31, Ludovic Brenta wrote:
> Nicolas Boulenguez writes:
>> A bootstrap issue will remain: building a new gnat-4.9 package
>> installing these symlinks requires a working compiler.
>
> I am now uploading gnat-4.9 4.9.1-2 which solves this problem. I
> bootstrapped it on a kfreebsd-i
Source: gnat-4.9
Version: 4.9.1-1
Severity: serious
I've noticed this build failures on kfreebsd-i386:
https://buildd.debian.org/status/fetch.php?pkg=apq&arch=kfreebsd-i386&ver=3.2.0-2&stamp=1409095293
https://buildd.debian.org/status/fetch.php?pkg=gnat-gps&arch=kfreebsd-i386&ver=5.3-3&stamp=1408
On 10/07/14 10:09, Matthias Klose wrote:
> clone 754263 -1
> reassign -1 src:gdcm
> severity 754263 important
> thanks
>
> Am 10.07.2014 09:58, schrieb Mathieu Malaterre:
>> Control: reassign -1 gcc-4.9 4.9.0-9
>>
>> On Thu, Jul 10, 2014 at 9:55 AM, Matthias Klose wrote:
>>> Control: reassign -1
Control: reassign -1 gcc4.8,gcc4.9
Hi,
This is still a problem with GCC 4.9. Is there any progress on this? This is
making aegisub FTBFS on armel, blocking the libass transition.
Cheers,
Emilio
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
Control: severity -1 serious
This is causing various packages to FTBFS (brltty, qdbm, possibly others), hence
bumping the severity.
Emilio
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http
On 14/08/10 12:45, Matthias Klose wrote:
severity 589389 important
tag 589389 + moreinfo help
thanks
lowering severity, workaround is available.
the preprocessed source is missing, and the information is missing, if
the issue is fixed in gcc-4.5 and in gcc-snapshot (4.6).
As I said the issue w
On 08/08/10 18:23, Emilio Pozuelo Monfort wrote:
> I've debugged it on merulo and it builds fine with gcc-4.3 and gcc-snapshot,
> only fails with gcc-4.4. However with -O0 and -O1 it builds fine with
> gcc-4.4, only -O2 fails.
FWIW this was with gcc-4.4 4.4.4-7 (the one that i
Matthias Klose wrote:
> Emilio Pozuelo Monfort schrieb:
>> I'll look into gcc-4.4 and gcc-4.3 next.
OK, here they are.
I've tested both only on i386 (I don't have any other arch right now). They seem
to work fine (pass build-id by default, can be overridden with
-Wl,--b
reassign 535237 gcc-snapshot
retitle 535237 gcc: pass --build-id to the linker whenever possible
notfound 535237 2.19.1-1
thanks
Let's reassign this to gcc to pass -Wl,--build-id when the linker supports it.
We will see if we can/need to change ld too.
Emilio Pozuelo Monfort wrote:
> By
19 matches
Mail list logo
