Bug#112887: marked as done (gcc in alternatives?)
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; 20 Sep 2001 10:05:25 +0000
>From avbidder@vis.ethz.ch Thu Sep 20 05:05:25 2001
Return-path: <avbidder@vis.ethz.ch>
Received: from naboo.ethz.ch [129.132.17.66]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15k0hw-0003e4-00; Thu, 20 Sep 2001 05:05:24 -0500
Received: by naboo.ethz.ch (Postfix, from userid 246)
id C00E1275B6; Thu, 20 Sep 2001 12:05:22 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by naboo.ethz.ch (Postfix) with ESMTP id BA8DD2659C
for <submit@bugs.debian.org>; Thu, 20 Sep 2001 12:05:22 +0200 (CEST)
Date: Thu, 20 Sep 2001 12:05:22 +0200 (CEST)
From: Adrian von Bidder <avbidder@vis.ethz.ch>
X-Sender: avbidder@naboo.ethz.ch
Reply-To: avbidder@fortytwo.ch
To: submit@bugs.debian.org
Subject: gcc in alternatives?
Message-ID: <Pine.LNX.4.21.0109201202140.472-100000@naboo.ethz.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: submit@bugs.debian.org
Package: gcc-3.0
Severity: wishlist
Version: 1:3.0.2-0pre010908
Hi!
I would be glad if gcc would install itself in the Debian alternatives
system. gcc-3.0 is quite stable, and I would like to test it by using it as
my standard compiler; as it does not set /usr/bin/gcc (and rightly so), I
thought it would be really nice to have alternatives.
Thank you.
-- vbi
---------------------------------------
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: