Clang 3.2 spurious depends on libgcc-4.7-dev from Experimental

[Sylvestre Ledru]

On 21/12/2012 05:44, Marc J. Driftmeyer wrote:
> To who it may concern,
> 
> I am trying to discern what sensible reason you are requiring
> libgcc-4.7-dev which pulls in 4.7.2-15 from Experimental to install
> clang-3.2 release.
> 
> I wasted an entire week on dealing with broken path issues for vector,
> stdio and more because of this crap, downgraded back to Sid's 4.7.2-4
> and LLVM/Clang Trunk builds cleanly with gcc and thus allows me to then
> self-host with clang/clang++ freshly created from then on out.
> 
> There should be no reason to deal with gcc-4.7 experimental:
Actually, yes.
Since 4.7.2-10, gcc-4.7 introduced these changes:
  * Split out lib*gcc-dev packages.
  * Split out lib*objc-dev packages.
  * Split out lib*gfortran-dev packages.
  * Split out lib*stdc++-dev packages.

This will allow clang to use only the dev packages.
For now, in testing, installing clang will also install g++.

Sylvestre