On Thu, 2018-03-08 at 14:54 -0800, Adam Williamson wrote: > While rebuilding stuff for "GCC 8 ABI change on x86_64", I noticed we > have a rather magnificent collection of ancient llvm versions: > > llvm34 > llvm35 > llvm3.9 > llvm4.0 > llvm5.0 > > None of these is retired (llvm33 and llvm3.7 also exist, but *are* > retired). llvm34 and llvm35 don't build successfully and haven't for > some time. The more recent ones mostly look like they should build, > except they have issues with exhausting RAM on the i686 and armhfp > builders. > > Do we actually need all of these for anything? Can we kill some of > them? AFAICS, nothing at all uses these: [adamw@adam llvm-3.4.2.src (master %)]$ sudo dnf repoquery --enablerepo=fedora-source --whatrequires llvm35 Last metadata expiration check: 0:00:00 ago on Thu 08 Mar 2018 03:04:53 PM PST. llvm35-devel-0:3.5.2-4.fc26.i686 llvm35-devel-0:3.5.2-4.fc26.x86_64 llvm35-doc-0:3.5.2-4.fc26.noarch [adamw@adam llvm-3.4.2.src (master %)]$ sudo dnf repoquery --enablerepo=fedora-source --whatrequires llvm3.9 Last metadata expiration check: 0:00:05 ago on Thu 08 Mar 2018 03:04:53 PM PST. llvm3.9-devel-0:3.9.1-11.fc27.i686 llvm3.9-devel-0:3.9.1-11.fc27.x86_64 [adamw@adam llvm-3.4.2.src (master %)]$ sudo dnf repoquery --enablerepo=fedora-source --whatrequires llvm4.0 Last metadata expiration check: 0:00:12 ago on Thu 08 Mar 2018 03:04:53 PM PST. llvm4.0-devel-0:4.0.1-3.fc28.i686 llvm4.0-devel-0:4.0.1-3.fc28.x86_64 llvm4.0-doc-0:4.0.1-3.fc28.noarch [adamw@adam llvm-3.4.2.src (master %)]$ sudo dnf repoquery --enablerepo=fedora-source --whatrequires llvm5.0 Last metadata expiration check: 0:00:17 ago on Thu 08 Mar 2018 03:04:53 PM PST. llvm5.0-devel-0:5.0.1-4.fc28.i686 llvm5.0-devel-0:5.0.1-4.fc28.x86_64 llvm5.0-doc-0:5.0.1-4.fc28.noarch -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
