[...]
> > clang.debian.net lists 39 instances of these, though I think the buildd
> > is a bit behind so there are probably a few more.
>
> At least one more of the 432 "Not categorized" is also due to this
> missing feature in clang (reprepro). As clang seems to gives quite
> misleading error mes
* Colin Watson [130604 15:47]:
> On Wed, May 29, 2013 at 10:08:59PM +0200, Michael Tautschnig wrote:
> > I think this will likely improve code quality, hence I'm much in
> > favour of this, in particular when it comes to outright bugs. But a
> > non-negligible fraction of the build failures, I bel
On Wed, May 29, 2013 at 10:08:59PM +0200, Michael Tautschnig wrote:
> I think this will likely improve code quality, hence I'm much in
> favour of this, in particular when it comes to outright bugs. But a
> non-negligible fraction of the build failures, I believe, are due to
> the use of nested fun
Hi Sylvestre,
[...]
> I started to report them (with patches for now) with minor as severity:
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=clang-ftbfs;users=pkg-llvm-t...@lists.alioth.debian.org
>
You might want to take a look at
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=m...@deb
On 29/05/2013 19:05, Sylvestre Ledru wrote:
> Hello,
>
> With the recent setup of the parallel build infrastructure using clang
> instead of gcc [1], I would like to start to report
> bugs on packages failing to build with clang (with patches if possible).
> The severity would be minor.
> Of cours
Please do. Minor is fine (any non-RC bug severity would be fine with me).
Ondřej Surý
On 29. 5. 2013, at 19:05, Sylvestre Ledru wrote:
> Hello,
>
> With the recent setup of the parallel build infrastructure using clang
> instead of gcc [1], I would like to start to report
> bugs on packages fa
On Thursday, May 30, 2013 09:34:06 AM Paul Tagliamonte wrote:
> On Thu, May 30, 2013 at 06:36:32AM -0400, Scott Kitterman wrote:
> > In that case, I'd say they aren't bugs at all. It may be that a FTBFS
> > with
> > clang is a symptom of some underlying issue that should be addressed, but
> > I
>
On Thu, May 30, 2013 at 06:36:32AM -0400, Scott Kitterman wrote:
> In that case, I'd say they aren't bugs at all. It may be that a FTBFS with
> clang is a symptom of some underlying issue that should be addressed, but I
> don't think non-wishlist bugs should be filed ONLY on the basis of that
>
On Thursday, May 30, 2013 10:15:11 AM Sylvestre Ledru wrote:
> On 30/05/2013 01:51, Scott Kitterman wrote:
> > Sylvestre Ledru wrote:
> >> Hello,
> >>
> >> With the recent setup of the parallel build infrastructure using clang
> >> instead of gcc [1], I would like to start to report
> >> bugs on
On 30/05/2013 01:51, Scott Kitterman wrote:
>
>
> Sylvestre Ledru wrote:
>
>> Hello,
>>
>> With the recent setup of the parallel build infrastructure using clang
>> instead of gcc [1], I would like to start to report
>> bugs on packages failing to build with clang (with patches if
>> possible).
Sylvestre Ledru wrote:
>Hello,
>
>With the recent setup of the parallel build infrastructure using clang
>instead of gcc [1], I would like to start to report
>bugs on packages failing to build with clang (with patches if
>possible).
>The severity would be minor.
>Of course, I would do that only
> Hello,
>
> With the recent setup of the parallel build infrastructure using clang
> instead of gcc [1], I would like to start to report
> bugs on packages failing to build with clang (with patches if possible).
> The severity would be minor.
> Of course, I would do that only when the issue is up
On Wed, May 29, 2013 at 07:05:18PM +0200, Sylvestre Ledru wrote:
> Hello,
>
> With the recent setup of the parallel build infrastructure using clang
> instead of gcc [1], I would like to start to report
> bugs on packages failing to build with clang (with patches if possible).
> The severity would
Hello,
With the recent setup of the parallel build infrastructure using clang
instead of gcc [1], I would like to start to report
bugs on packages failing to build with clang (with patches if possible).
The severity would be minor.
Of course, I would do that only when the issue is upstream [2].
A
14 matches
Mail list logo
