[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#126675: gcc: please honor user's gcc symlink setting



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 after woody's release all the same.  I've been using it since
> > the release of 3.0.2 and have had it break only on some #define abuse in
> > epic and a few things that were clearly broken such as var = var = value
> > and that like.
> > 
> > Please consider it, at any rate.
> 
> sure, after woody, we will change the default gcc/g++. But probably to
> gcc-3.1, when this version is released in April 2002. I think it does
> not make sense to switch to 3.0 in (say February) and then again in
> April.

That's perfectly fine, especially given that that a new compiler version
can be expected to break a partial make and auto* will not know it needs
to rebuild everything.

-- 
Joseph Carter <knghtbrd@bluecherry.net>      Intelligent backside at large
 
<Knghtbrd> Studies prove that research causes cancer in 43% of laboratory
           rats
<CQ> knghtbrd- yeah, but 78% of those statistics are off by 52%...

Attachment: pgp9q4N2c5Cuz.pgp
Description: PGP signature


Reply to: