Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47562 - clang and clang35 should not conflict with each other
Attached to Project:
Arch Linux
Opened by pavan yalamanchili (pavanky) - Tuesday, 29 December 2015, 22:27 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 30 December 2015, 01:10 GMT
Opened by pavan yalamanchili (pavanky) - Tuesday, 29 December 2015, 22:27 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 30 December 2015, 01:10 GMT
|
DetailsInstead of clang35 replacing clang, can it not be installed as clang3.5 ? Users wanting clang35 can set CC=clang35 and build their programs.
The llvm dependencies for these packages already co-exist with each other. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 30 December 2015, 01:10 GMT
Reason for closing: Not a bug
Additional comments about closing: They provide the same files, so they conflict. It's only in the repos for when it's needed as a makedep in a clean chroot.
Wednesday, 30 December 2015, 01:10 GMT
Reason for closing: Not a bug
Additional comments about closing: They provide the same files, so they conflict. It's only in the repos for when it's needed as a makedep in a clean chroot.