This is evil ;-)
I agree. It would be better if c++config.h would take compiler and
library configurations into account. For *-*-linux-gnu, c++config.h
should contain fragments like
#ifdef __USE_ISOC99
#define _GLIBCPP_USE_C99 1
#endif
That would remove the need to define _GNU_SOURCE in the
merge 126675 112887
tags 126675 + wontfix
thanks
using dpkg-divert should work even when upgrading the package.
Joseph Carter writes:
Package: gcc
Version: 2:2.95.4-9
Severity: wishlist
I have changed the gcc symlink on my system to point to gcc-3.0 to help
work out the kinks with the
Processing commands for [EMAIL PROTECTED]:
merge 126675 112887
Bug#112887: gcc in alternatives?
Bug#126675: gcc: please honor user's gcc symlink setting
Bug#115353: gcc: cc gcc should use update-alternatives mechanism
Bug#119952: gcc-3.0: could gcc-3.0 be hooked into the alternatives system?
Submitter-Id: net
Originator:Marcus Brinkmann
Organization: To organize is to destroy.
Confidential: no
Synopsis: profiling support for i386-gnu specs file
Severity: non-critical
Priority: low
Category: target
Class: sw-bug
Release: 3.0.2 (Debian) (Debian
Joseph Carter writes:
On Fri, Dec 28, 2001 at 02:37:31PM +0100, Matthias Klose wrote:
using dpkg-divert should work even when upgrading the package.
That's a bit less hackish I suppose than futzing with the symlink
directly, but I still believe /etc/alternatives would be a good thing
here.
On Fri, Dec 28, 2001 at 09:11:46PM +0100, Matthias Klose wrote:
That's a bit less hackish I suppose than futzing with the symlink
directly, but I still believe /etc/alternatives would be a good thing
here. If you disagree, that's fine, but I'd ask that the gcc symlink move
to gcc-3.0
6 matches
Mail list logo
