-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, While in the past I've shied away from bumping the LLVM version shipping with a Fedora release, it appears that there are enough users using Clang++ that the post-release breakage that happens when gcc-c++/libstdc++ is updated is really a chronic problem. Between backporting the patches in question, and rebuilding the entire stack of LLVM and dependent apps, it seems to me that on balance it might be easier to do the rebuilding - though I'd need the help of proven testers to test the critical path updates involving LLVM and mesa-llvmpipe (by running a F17 installation under KVM). Sending this to the relevant package owners as well as the development list - if there's too much pushback, I'll look at backporting the patches instead, though given that LLVM 3.2 is scheduled for release next month, if we agree, going forward, that occasional stack rebuilds are acceptable, it would really lower the maintenance burden, instead of having to support 3 LLVM releases. Thanks, - -- Michel Alexandre Salim Fedora Project Contributor: http://fedoraproject.org/ Email: salimma@xxxxxxxxxxxxxxxxx | GPG key ID: A36A937A Jabber: hircus@xxxxxxxxxxxxx | IRC: hircus@xxxxxxxxxxxxxxxx () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQpgO8AAoJEEr1VKujapN6v3UH/3ccA5OqMOiiQQhPUjtZ6Sn3 LzLipnsn445EIpLGmRd7nW45Yb6b9U0tHSUp/QxbN50+aQBitf+7mjzr6FkgYxJC 7mLAIGaOuadYnS4XoLZqfVpZ5MoPWii7ei2gUVjwn14Z6NJGR2axO+vFhm9I73KZ ak0JNO3EsvT0plFKl8QBw7jhYv1wvOk1ndwP6KSrPS4r1V1qW9VIEtFjEsFqsun9 qhd2IySbRvDiVw4cdvfOlE+L3Ljym8ie4CrOKixgq8rwViKG9G1jNKsWQ398OWOi Vj1hkTD/wtHrO1hZtF/rfD8izOaN4y+REwSkMCDNp+poE8cK9QkxySVmCYKca6o= =6yIa -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
