Summary: | [bsd.port.mk] Add bsd.clang.mk with Clang/LLVM support | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | kamikaze | ||||||
Component: | Individual Port(s) | Assignee: | Port Management Team <portmgr> | ||||||
Status: | Closed FIXED | ||||||||
Severity: | Affects Only Me | ||||||||
Priority: | Normal | ||||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Description
kamikaze
2011-10-30 22:50:10 UTC
Add bsd.port.mk inclusion patch, because it didn't trigger the GNATS magic in the OP. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? State Changed From-To: open->suspended portmgr territory. This should be discussed on the mailing list prior to reopening it. Thanks for looking into this. I'm sure portmgr will have a lot more to say - I know they did with my version of a similar patch ;) Responsible Changed From-To: freebsd-ports-bugs->portmgr portmgr territory. This should be discussed on the mailing list prior to reopening it. Thanks for looking into this. I'm sure portmgr will have a lot more to say - I know they did with my version of a similar patch ;) We now have compiler.mk, do we still need bsd.clang.mk regards, Bapt On 29/12/2013 00:43, Baptiste Daroussin wrote:
> We now have compiler.mk, do we still need bsd.clang.mk
Due to the deployment of cc=clang in FreeBSD 10 it's obsolete, as
far as I'm concerned.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
State Changed From-To: suspended->closed close by submitter request. |