Bug#115353: marked as done (gcc: cc & gcc should use update-alternatives mechanism)
Your message dated Tue, 29 Jul 2003 22:25:26 +0200
with message-id <16166.55350.626818.320744@gargle.gargle.HOWL>
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; 12 Oct 2001 11:05:24 +0000
>From marko@l-t.ee Fri Oct 12 06:05:24 2001
Return-path: <marko@l-t.ee>
Received: from a030.pro.comtrade.ee (snoopy.jura.ee) [212.47.217.30] (james)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15s07i-0005UF-00; Fri, 12 Oct 2001 06:05:22 -0500
Received: from marko by snoopy.jura.ee with local (Exim 3.32 #1 (Debian))
id 15rzvX-000356-00; Fri, 12 Oct 2001 12:52:27 +0200
From: marko <marko@l-t.ee>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: gcc: cc & gcc should use update-alternatives mechanism
X-Reportbug-Version: 1.30
X-Mailer: reportbug 1.30
Date: Fri, 12 Oct 2001 12:52:26 +0200
Message-Id: <E15rzvX-000356-00@snoopy.jura.ee>
Delivered-To: submit@bugs.debian.org
Package: gcc
Version: 2:2.95.4-6
Severity: wishlist
As in subject: I think that cc and gcc should be provided
through update-alternatives mechanism, so user could
switch between gcc272, gcc-2.95 and gcc-3.0 more easily.
Eg. use gcc-3.0 for cc but gcc-2.95 for gcc or whatever...
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux snoopy 2.4.11 #1 Wed Oct 10 18:21:21 EET 2001 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages gcc depends on:
ii cpp 2:2.95.4-6 The GNU C preprocessor.
ii cpp-2.95 1:2.95.4-0.010810 The GNU C preprocessor.
ii gcc-2.95 1:2.95.4-0.010810 The GNU C compiler.
---------------------------------------
Received: (at 119952-done) by bugs.debian.org; 29 Jul 2003 20:26:38 +0000
>From doko@cs.tu-berlin.de Tue Jul 29 15:26:35 2003
Return-path: <doko@cs.tu-berlin.de>
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 (daemon@bolero.cs.tu-berlin.de [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 doko@localhost)
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 <doko@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16166.55350.626818.320744@gargle.gargle.HOWL>
Date: Tue, 29 Jul 2003 22:25:26 +0200
To: Jochen Voss <jvoss2@web.de>, 119952-done@bugs.debian.org
Subject: Re: Bug#119952: should bug #119952 be closed?
In-Reply-To: <[🔎] 20030727170430.GA1181@localhost>
References: <[🔎] 20030727170430.GA1181@localhost>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: 119952-done@bugs.debian.org
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 to: