[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#135943: marked as done (gcc on m68k has internal error in coxfit2.c in survival in r-recommended)



Your message dated Wed, 27 Feb 2002 00:13:15 -0800
with message-id <20020227081315.GA4766@def.debian.net>
and subject line Processed: Re: Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Feb 2002 20:00:48 +0000
>From rick@def.debian.net Tue Feb 26 14:00:48 2002
Return-path: <rick@def.debian.net>
Received: from group40.vcn.bc.ca (def.debian.net) [207.102.64.104] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16fnmI-0007CW-00; Tue, 26 Feb 2002 14:00:48 -0600
Received: from rick by def.debian.net with local (Exim 3.34 #1 (Debian))
	id 16fnm8-00071A-00
	for <submit@bugs.debian.org>; Tue, 26 Feb 2002 12:00:36 -0800
Date: Tue, 26 Feb 2002 12:00:32 -0800
From: Rick Younie <rick@def.debian.net>
To: submit@bugs.debian.org
Subject: r-recommended_1.4.1-1 fails to autobuild on m68k
Message-ID: <20020226200032.GA26854@def.debian.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Delivered-To: submit@bugs.debian.org

Package: r-recommended
Version: 1.4.1-1

Hi,

Changing optimization for m68k to -O1 gets past the ICE at least;
it may even allow the package to build.  CFLAGS is ignored though
and I can't patch any other file because the patch is applied
when the source is first unpacked and everything is tarballs.  Do
you see an easy way to do this?

Rick
-- 

---------------------------------------
Received: (at 135943-done) by bugs.debian.org; 27 Feb 2002 08:13:27 +0000
>From rick@def.debian.net Wed Feb 27 02:13:27 2002
Return-path: <rick@def.debian.net>
Received: from group29.vcn.bc.ca (def.debian.net) [207.102.64.93] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16fzDK-0003o9-00; Wed, 27 Feb 2002 02:13:27 -0600
Received: from rick by def.debian.net with local (Exim 3.34 #1 (Debian))
	id 16fzD9-0001Ia-00; Wed, 27 Feb 2002 00:13:15 -0800
Date: Wed, 27 Feb 2002 00:13:15 -0800
From: Rick Younie <rick@def.debian.net>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: 135943-done@bugs.debian.org, Dirk Eddelbuettel <edd@debian.org>
Subject: Re: Processed: Re: Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k
Message-ID: <20020227081315.GA4766@def.debian.net>
References: <15484.18232.67728.808933@sonny.eddelbuettel.com> <[🔎] handler.s.C.101477765728055.transcript@bugs.debian.org> <[🔎] 15484.32308.674769.247044@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 15484.32308.674769.247044@gargle.gargle.HOWL>
User-Agent: Mutt/1.3.27i
Delivered-To: 135943-done@bugs.debian.org

Matthias Klose wrote:
> Debian Bug Tracking System writes:
> > Processing commands for control@bugs.debian.org:
> > 
> > > reassign 135943 gcc
> > Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k
> > Bug reassigned from package `r-recommended' to `gcc'.
> > 
> > > retitle 135943 gcc on m68k has internal error in coxfit2.c in survival in r-recommended
> 
> If live is so short, why the hell does noone of you attach the
> preprocessed source to the report, when reassigning the report to
> gcc???? You are no Debian newbies. Just wondering ...
> 
> and recheck with gcc-3.0 ...

Hi,

I'm trying to get some long-term failures built between buildd
runs before the freeze.  m68k certainly isn't the only arch with
bugs in the optimizing code and a tweak probably would have built
this package.

The build system it uses doesn't make any sense to me, even
to change optimizing or compiler.  If I get time I'll take
the tarballs apart have a go.  I'll file a decent bug report
then.

Closing this bug.

Rick
-- 



Reply to: