changes to clang and llvm ports

Brooks Davis brooks at freebsd.org
Fri Oct 18 22:56:02 UTC 2013


You are recieving this message because you maintain a port that users
devel/llvm, devel/llvm31, lang/clang, or lang/clang31.

I've added two new ports devel/llvm32 and lang/clang32 which will soon
replace devel/llvm and devel/clang.  They are identical except that they
have different paths so they don't conflict with other ports and the programs
installed in ${PREFIX}/bin are suffixed with "32" (i.e. llvm-config32,
clang32).  If your port users the old conflicting versions it should
stop doing so and switch to an appropriate non-conflicting port.

I plan to similarly modify devel/llvm31 and devel/clang31 so pure and
clay will need to be modified along with that commit.

In general, ports that already use llvm-config should just need to be
told to use the correct one.  Other ports should likely be able to get
by with setting CC, CXX, etc.

Once the new ports are in place I will try to find some time to
implement appropriate USES=clang and llvm functionality, but I haven't
thought about that in much detail yet.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-office/attachments/20131018/5e9213fa/attachment.sig>


More information about the freebsd-office mailing list