On Thu, Jun 05, 2014 at 03:00:57PM +0200, Ludovic Courtès wrote:
> It’s been discussed several times, but there’s no satisfactory solution
> so far.  Changing the name seems like a bad idea, because it’s really
> gcc.  Making either gcc-final or gcc-4.8 private isn’t an option because
> they’re referred from elsewhere.

Sorry for my forgetfulness. So the references to gcc-4.8 could not be replaced
by references to gcc-final? Notice, for instance, that gcc-toolchain-4.8 does
not use gcc-4.8, but gcc-final already.

Andreas


Reply via email to