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

Bug#101637: marked as done (Cannot resume after failure in binary-libstdcxx.mk)

Your message dated Sun, 24 Jun 2001 22:04:09 +0200
with message-id <15158.18361.696449.661814@gargle.gargle.HOWL>
and subject line fixed in gcc-3.0-2
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.)

Darren Benham
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 20 Jun 2001 16:21:18 +0000
>From jbailey@olympus.nisa.net Wed Jun 20 11:21:18 2001
Return-path: <jbailey@olympus.nisa.net>
Received: from olympus.nisa.net [::ffff:] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 15CkjG-0008Es-00; Wed, 20 Jun 2001 11:21:18 -0500
Received: (from jbailey@localhost)
	by olympus.nisa.net (8.10.2/8.10.2) id f5KGKsI02547
	for submit@bugs.debian.org; Wed, 20 Jun 2001 09:20:54 -0700
Date: Wed, 20 Jun 2001 09:20:54 -0700
From: Jeff Bailey <jbailey@nisa.net>
To: submit@bugs.debian.org
Subject: Cannot resume after failure in binary-libstdcxx.mk
Message-ID: <20010620092054.E2422@nisa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Delivered-To: submit@bugs.debian.org

Package: gcc-3.0
Version: 3.0.ds8-0pre010613

While porting to the Hurd, I came across a bug in binary-libstdcxx.mk.
I corrected the bug and reran `debian/rules binary-arch'.  However,
because it had *already* moved some files around, it's not capable of
resuming where it was after a failure.

(These fixes will be sent in a seperate bug report...)

I suspect the best fix is to 'rm 07-install-stamp' at the beginning of
each new section where files are moved around, and then touch it again
when everything is in a resumable state again.  The install step could
then still skip the succesful sections that had been copied correctly.

Jeff Bailey

Received: (at 101637-done) by bugs.debian.org; 24 Jun 2001 20:08:28 +0000
>From doko@cs.tu-berlin.de Sun Jun 24 15:08:27 2001
Return-path: <doko@cs.tu-berlin.de>
Received: from mail.cs.tu-berlin.de [::ffff:] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 15EGBD-0002jv-00; Sun, 24 Jun 2001 15:08:23 -0500
Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [])
	by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id WAA06912;
	Sun, 24 Jun 2001 22:04:10 +0200 (MET DST)
Received: (from doko@localhost)
	by bolero.cs.tu-berlin.de (8.10.2+Sun/8.9.3) id f5OK49q22629;
	Sun, 24 Jun 2001 22:04:09 +0200 (MEST)
From: Matthias Klose <doko@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15158.18361.696449.661814@gargle.gargle.HOWL>
Date: Sun, 24 Jun 2001 22:04:09 +0200
To: 102041-done@bugs.debian.org, 101534-done@bugs.debian.org,
        101570-done@bugs.debian.org, 101708-done@bugs.debian.org,
        101711-done@bugs.debian.org, 101557-done@bugs.debian.org,
        101901-done@bugs.debian.org, 101743-done@bugs.debian.org,
Subject: fixed in gcc-3.0-2
X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Delivered-To: 101637-done@bugs.debian.org

  * Add libgcc0 and libgcc300 to the build conflicts (#102041).
  * debian/README.FIRST: Removed (#101534).
  * Updated subreg-byte patch (doc files).
  * Disable java for the Hurd, mips and mipsel (#101570).
  * Patch for building on the Hurd (#101708) (Jeff Bailey <jbailey@nisa.net>).
  * Packaging fixes for the Hurd (#101711) (Jeff Bailey <jbailey@nisa.net>).
  * Include pregenerated doxygen (1.2.6) docs for libstdc++-v3 (#101557).
    The current doxygen- segaults.
  * C++: Enable -fuse-cxa-atexit by default (#101901).
  * Correct mail address in gccbug (#101743).
  * Make rules resumable after failure in binary-xxx targets (#101637).

Reply to: