On Sun, Oct 23, 2005 at 12:41:18PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> > the best option, I'm game. One disadvantage is that it wouldn't let us get
> > feedback about what
Matthias Klose <[EMAIL PROTECTED]> writes:
>> > ahh, ok. so you did check that defaulting to g++-3.4 on these archs
>> > doesn't reveal another RC bug and we should remove g++-3.4 on these
>> > archs as well?
>>
>> Nope, did you when you told me to downgrade my package to use g++-3.4?
>>
>> I me
Thomas Bushnell BSG writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> > Thomas Bushnell BSG writes:
> >> Steve Langasek <[EMAIL PROTECTED]> writes:
> >>
> >> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs
> >> > is
> >> > the best option, I'm game. One disadva
Matthias Klose <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG writes:
>> Steve Langasek <[EMAIL PROTECTED]> writes:
>>
>> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
>> > the best option, I'm game. One disadvantage is that it wouldn't let us get
>> > feedback
Thomas Bushnell BSG writes:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> > the best option, I'm game. One disadvantage is that it wouldn't let us get
> > feedback about what else might be wrong with g++-4.0 on tho
Steve Langasek <[EMAIL PROTECTED]> writes:
> If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> the best option, I'm game. One disadvantage is that it wouldn't let us get
> feedback about what else might be wrong with g++-4.0 on those architectures,
> but we probably al
Processing commands for [EMAIL PROTECTED]:
> tags 335286 - fixed-upstream
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Tags were: upstream fixed-upstream
Bug#323133: [PR 21123, 4.0 regression, fixed in 4.1] ICE on arm & m68k when
compiling arts (in cp_expr_size, at cp/c
tags 335286 - fixed-upstream
tags 335286 + help
thanks
Steve Langasek writes:
> On Sat, Oct 22, 2005 at 11:18:00PM -0700, Thomas Bushnell BSG wrote:
> > I find it ludicrous to think that the best solution here is to force a
> > jillion maintainers to workaround the bug and recompile.
>
> I would
On Sat, Oct 22, 2005 at 11:18:00PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > This is the single most common build failure on arm, hppa, and m68k right
> > now, and has affected literally dozens or hundreds of other packages. I
> > do kinda know it on sight
Steve Langasek <[EMAIL PROTECTED]> writes:
> This is the single most common build failure on arm, hppa, and m68k right
> now, and has affected literally dozens or hundreds of other packages. I
> do kinda know it on sight by this point.
>
>> Moreover, this bug should remain filed against gcc-4.0,
Processing commands for [EMAIL PROTECTED]:
> severity 335286 important
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Severity set to `important'.
> merge 335286 323133
Bug#323133: [PR 21123, 4.0 regression, fixed in 4.1] ICE on arm & m68k when
compiling arts (
severity 335286 important
merge 335286 323133
thanks
On Sat, Oct 22, 2005 at 09:59:30PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > reassign 335286 lilypond
> > thanks
> > On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
> >> Compiling l
Processing commands for [EMAIL PROTECTED]:
> reassign 335286 gcc-4.0
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Bug reassigned from package `lilypond' to `gcc-4.0'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
> reassign 335286 lilypond
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Bug reassigned from package `gcc-4.0' to `lilypond'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
reassign 335286 lilypond
thanks
On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
> Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
> See:
> http:://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=hppa&stamp=1130038470&file=log&as=raw
> Severity
reassign 335286 gcc-4.0
thanks
Steve Langasek <[EMAIL PROTECTED]> writes:
> reassign 335286 lilypond
> thanks
>
> On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
>
>> Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
>
>> See:
>> http:://buildd.debian.org/fe
Package: gcc-4.0
Version: 4.0.2-2
Severity: serious
Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
See:
http:://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=hppa&stamp=1130038470&file=log&as=raw
Severity serious because this creates an FTBFS situation for lilyp
17 matches
Mail list logo
