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

[Marc J. Driftmeyer]

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:

> (Reading database ... 1052245 files and directories currently installed.)
> Unpacking clang-3.2 (from clang-3.2_3.2-1~exp1_amd64.deb) ...
> dpkg: dependency problems prevent configuration of clang-3.2:
>  clang-3.2 depends on libgcc-4.7-dev; however:
>   Package libgcc-4.7-dev is not installed.
>  clang-3.2 depends on libobjc-4.7-dev; however:
>   Package libobjc-4.7-dev is not installed.
>  clang-3.2 depends on libclang-common-dev (= 3.2-1~exp1); however:
>   Version of libclang-common-dev on system is 3.1-8.
>
> dpkg: error processing clang-3.2 (--install):
>  dependency problems - leaving unconfigured
> Processing triggers for man-db ...
> Errors were encountered while processing:
>  clang-3.2

This is an erroneous depends that makes no sense. Nothing in clang 
requires the latest backport fixes from gcc-4.8 into gcc-4.7.2 to build 
LLVM/Clang trunk.

What am I misunderstanding here?

Sincerely,

Marc J. Driftmeyer


-- 
Marc J. Driftmeyer
Email :: mjd at reanimality.com <mailto:mjd at reanimality.com>
Web :: http://www.reanimality.com
Cell :: (509) 435-5212
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-llvm-team/attachments/20121220/27e221e3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjd.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-llvm-team/attachments/20121220/27e221e3/attachment.vcf>