Your message dated Sun, 2 Jun 2002 01:05:18 +0200 (MEST)
with message-id <[EMAIL PROTECTED]>
and subject line don't package egcs
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; 5 Jan 2001 21:08:05 +0000
>From [EMAIL PROTECTED] Fri Jan 05 15:08:05 2001
Return-path: <[EMAIL PROTECTED]>
Received: from 209-130-132-249.nas3.roc.gblx.net (phoenix.overdue.net) 
[209.130.132.249] (postfix)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 14Ee5f-0005Sf-00; Fri, 05 Jan 2001 15:08:00 -0600
Received: by phoenix.overdue.net (Postfix, from userid 1002)
        id 21DAE3088F; Fri,  5 Jan 2001 21:07:54 +0000 (UTC)
From: Lazarus Long <[EMAIL PROTECTED]>
Subject: gcc272: gcc29166
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.7
Message-Id: <[EMAIL PROTECTED]>
Date: Fri,  5 Jan 2001 21:07:54 +0000 (UTC)
Delivered-To: [EMAIL PROTECTED]

Package: gcc272
Version: 2.7.2.3-16
Severity: wishlist

Since we have gcc272 available for us, specifically for kernel compiles,
please also add a "safe" gcc package for kernel 2.4.x compiling.

Note that I'm *not* asking for gcc272 to go away, since many will still
choose to run 2.2.x and 2.0.x kernels, especially those with resource
contraints.

>From kernel-source-2.4.0/README:

 - Make sure you have gcc-2.91.66 (egcs-1.1.2) available.  gcc 2.95.2 may
   also work but is not as safe, and *gcc 2.7.2.3 is no longer supported*.
   Also remember to upgrade your binutils package (for as/ld/nm and company)
   if necessary. For more information, refer to ./Documentation/Changes.

"may" and "is not as safe" are inappropriate for kernel compilation.

Would you please package a kernel-safe compiler for the 2.4.x series,
just as we now have in the gcc272 package for the 2.0.x and 2.2.x
series kernels?

-- System Information
Debian Release: post-2.2
Kernel Version: Linux phoenix 2.2.18 #1 Sat Dec 23 14:59:36 UTC 2000 i586 
unknown

Versions of the packages gcc272 depends on:
ii  binutils       2.10.1.0.2-1   The GNU assembler, linker and binary utiliti
ii  dpkg           1.8.1          Package maintenance system for Debian
ii  libc6          2.2-9          GNU C Library: Shared libraries and Timezone

---------------------------------------
Received: (at 74426-done) by bugs.debian.org; 1 Jun 2002 23:07:35 +0000
>From [EMAIL PROTECTED] Sat Jun 01 18:07:35 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 17EHyA-0008Rk-00; Sat, 01 Jun 2002 18:07:35 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
        by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id BAA12840
        for <[EMAIL PROTECTED]>; Sun, 2 Jun 2002 01:05:19 +0200 (MET DST)
Resent-From: Matthias Klose <[EMAIL PROTECTED]>
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id g51N5Ie25731;
        Sun, 2 Jun 2002 01:05:18 +0200 (MEST)
Date: Sun, 2 Jun 2002 01:05:18 +0200 (MEST)
Message-Id: <[EMAIL PROTECTED]>
Resent-Message-ID: <[EMAIL PROTECTED]>
Resent-Date: Sun, 2 Jun 2002 01:05:18 +0200
Resent-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Matthias Klose <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: don't package egcs
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]

with gcc-3.1 and -3.0 in unstable, I'll close this report ...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to