Date: Sun, 10 Feb 2013 19:11:27 GMT From: Shane Ambler <FreeBSD@Shaneware.biz> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/176017: Remove conflicts between llvm/clang versions Message-ID: <201302101911.r1AJBRMn007370@red.freebsd.org> Resent-Message-ID: <201302101920.r1AJK0ra098829@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 176017 >Category: ports >Synopsis: Remove conflicts between llvm/clang versions >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Feb 10 19:20:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Shane Ambler >Release: 9.1-RELEASE >Organization: >Environment: FreeBSD leader.local 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r246600: Sun Feb 10 16:13:27 CST 2013 shane@leader.local:/usr/obj/usr/src/sys/dtracekern amd64 >Description: I believe that the conflicts between clang and llvm versions needs to be removed. As new version become available the desire to have multiple versions installed for testing and supporting older code will increase. The technique used for gcc versions should be re-produced so we end up with the base version as clang and the ports versions as clang31 clang32 clang++31 clang++32... The same thing should be applied to llvm. While the main llvm lib has a version in the filename the other libs either need to be named similarly or moved into a versioned dir. This should be considered while the use of clang/llvm is still early. As more ports are changed to use clang it will be harder to make the switch later. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201302101911.r1AJBRMn007370>