Your message dated Wed, 6 Jul 2005 10:27:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gcc symlink will not be managed by alternatives
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 Aug 2004 16:49:42 +0000
>From [EMAIL PROTECTED] Thu Aug 12 09:49:42 2004
Return-path: <[EMAIL PROTECTED]>
Received: from freyja.ed.aculab.com [62.189.57.200] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BvIlp-0002P0-00; Thu, 12 Aug 2004 09:49:41 -0700
Received: from frigga.ed.aculab.com (jormungand.ed.aculab.com [62.189.57.201])
        (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
        (No client certificate requested)
        by freyja.ed.aculab.com (Postfix) with ESMTP
        id A2017BFC91; Thu, 12 Aug 2004 17:56:16 +0100 (BST)
Received: from localhost (localhost [127.0.0.1])
        by frigga.ed.aculab.com (Postfix) with ESMTP id 3294D623EB;
        Thu, 12 Aug 2004 17:49:38 +0100 (BST)
Received: from frigga.ed.aculab.com ([127.0.0.1])
        by localhost (frigga.ed.aculab.com [127.0.0.1]) (amavisd-new, port 
10024)
        with ESMTP id 09219-03; Thu, 12 Aug 2004 17:49:36 +0100 (BST)
Received: from rakim.ed.aculab.com (unknown [192.168.3.134])
        by frigga.ed.aculab.com (Postfix) with ESMTP;
        Thu, 12 Aug 2004 17:49:36 +0100 (BST)
Received: by rakim.ed.aculab.com (Postfix, from userid 12345)
        id 89593DF504; Thu, 12 Aug 2004 17:47:20 +0100 (BST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mark Brown <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc-3.4: Doesn't provide a /usr/bin/cc alternative
X-Mailer: reportbug 2.63
Date: Thu, 12 Aug 2004 17:47:20 +0100
Message-Id: <[EMAIL PROTECTED]>
X-Aculab-Com-Scanned: by amavisd-new-20030616-p10 (Debian) at aculab.com
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: gcc-3.4
Version: 3.4.1-5
Severity: minor

When installed on a system with no other C compilers installed the
gcc-3.4 package will not create an alternative for /usr/bin/cc, meaning
that things that rely on that being there won't work even though there
is in fact a C compiler installed.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=C, LC_CTYPE=C

Versions of packages gcc-3.4 depends on:
ii  binutils                    2.15-1       The GNU assembler, linker and bina
ii  cpp-3.4                     3.4.1-5      The GNU C preprocessor
ii  gcc-3.4-base                3.4.1-5      The GNU Compiler Collection (base 
ii  libc6                       2.3.2.ds1-13 GNU C Library: Shared libraries an
ii  libgcc1                     1:3.4.1-5    GCC support library

-- no debconf information

---------------------------------------
Received: (at 265318-done) by bugs.debian.org; 6 Jul 2005 08:27:29 +0000
>From [EMAIL PROTECTED] Wed Jul 06 01:27:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Dq5Fg-0004ES-00; Wed, 06 Jul 2005 01:27:28 -0700
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
        by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id KAA29752
        for <[EMAIL PROTECTED]>; Wed, 6 Jul 2005 10:27:25 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
        by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 4A5DCFD37
        for <[EMAIL PROTECTED]>; Wed,  6 Jul 2005 10:27:25 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
 by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
 id 19579-16 for <[EMAIL PROTECTED]>;
 Wed,  6 Jul 2005 10:27:25 +0200 (MEST) 14053
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
        by mailhost.cs.tu-berlin.de (Postfix) with ESMTP
        for <[EMAIL PROTECTED]>; Wed,  6 Jul 2005 10:27:24 +0200 (MEST)
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j668RODf008635;
        Wed, 6 Jul 2005 10:27:24 +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: Wed, 6 Jul 2005 10:27:24 +0200
To: [EMAIL PROTECTED]
Subject: gcc symlink will not be managed by alternatives
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

/usr/share/doc/gcc/README.Debian.gz (gcc >= 4:4.0) now has a paragraph:

The symlinks in /usr/bin (gcc, g++, ...) are not handled using the
Debian alternative mechanism. There are differences in the
architecture specific ABI on some architectures and the C++ ABI
differs as well. Having the symlinks managed by alternatives doesn't
allow reliable builds with the same major/minor version of the
compiler. To use another compiler version, set the appropriate
environment variables as described above in the section "Practical
implications".


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

Reply via email to