Your message dated Tue, 29 Jul 2003 22:25:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#119952: should bug #119952 be closed?
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; 11 Nov 2001 01:40:53 +0000
>From [EMAIL PROTECTED] Sat Nov 10 19:40:53 2001
Return-path: <[EMAIL PROTECTED]>
Received: from cicero.e-mis.co.uk [212.240.194.162] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 162jcC-0004rt-00; Sat, 10 Nov 2001 19:40:53 -0600
Received: from plato.systems ([172.21.77.254] ident=mail)
        by cicero.e-mis.co.uk with esmtp (Exim 3.12 #1 (Debian))
        id 162jcB-0000lG-00
        for <[EMAIL PROTECTED]>; Sun, 11 Nov 2001 01:40:51 +0000
Received: from laptop by plato.systems with local (Exim 3.32 #1 (Debian))
        id 162jcB-0005nA-00
        for <[EMAIL PROTECTED]>; Sun, 11 Nov 2001 01:40:51 +0000
To: [EMAIL PROTECTED]
Subject: gcc-3.0: doesn't depend on gcc
Mail-Copies-To: never
From: James Troup <[EMAIL PROTECTED]>
Date: 11 Nov 2001 01:40:51 +0000
Message-ID: <[EMAIL PROTECTED]>
Lines: 10
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: James Troup (laptop) <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]

Package: gcc-3.0
Version: 1:3.0.2-3

All the <foo>-3.0 packages don't depend, recommend or even suggest the
<foo> packages making it possible (especially on hppa where -3.0 is
the default compiler) to install just gcc-3.0 and not have a gcc
symlink which is probably not a good thing?

-- 
James

---------------------------------------
Received: (at 119952-done) by bugs.debian.org; 29 Jul 2003 20:26:38 +0000
>From [EMAIL PROTECTED] Tue Jul 29 15:26:35 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 19hb3K-0005ZC-00; Tue, 29 Jul 2003 15:26: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 WAA17686;
        Tue, 29 Jul 2003 22:25:26 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id h6TKPQn21928;
        Tue, 29 Jul 2003 22:25:26 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 29 Jul 2003 22:25:26 +0200
To: Jochen Voss <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#119952: should bug #119952 be closed?
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-14.5 required=4.0
        tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
              REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_VM
        autolearn=ham version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 
(1.174.2.15-2003-03-30-exp)

Jochen Voss writes:
> Hello,
> 
> I suggest to simply close bug #119952 and friends.  It is tagged
> wontfix and you won't get many new copies, because gcc-3.0 becomes out
> of fashion, now.

fine with me. for the record here the explanation:

gcc-x.y doesn't use alternatives to make sure that the preferred
system compiler is used when calling 'gcc'. switching the compiler
may break your system (will break for C++). In most gcc-x.y versions
ABI's are different.

If you want to test gcc-x.y for a particular package,

- use CC=gcc-x.y CXX=g++-x.y when configuring/compiling a package

- make ~<user>/bin/gcc a symlink to gcc-x.y and add it to your path

- if you know what you do, there is the option to divert the gcc/g++
  links.

closing the reports, adding to our karma.


Reply via email to