|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
x11/tint2 port using clang
x11/tint2 added clang support after 12.2 version currently in ports. The clang announcement said that it was now the default compiler. I have been using tint2-14.5 on -current for about 6 weeks and would like to recompile with clang. x11/tint2 uses cmake.
bsd.port.mk(5) indicates that one can choose the compiler Quote:
With that background. 1. Do I need to specify clang in the Makefile or do anything special to cmake? 2. Any clang tests need to be run on the build? 3. If clang fails, does one specify gcc4 in the interim? |
|
||||
The compiler clang has been the default compiler for amd64 and i386 base AND ports since late July. If you have followed the July 29 entry of the Following -current FAQ, all of your installed packages will have been built by the clang compiler except those which still require to be built by gcc 4.9 or gcc 4.2.
|
|
|||
Quote:
Quote:
No. No. Unless the project has hard dependencies on GNU C features that clang will never support (these things actually exist...), then you'd set COMPILER=gcc-only. But you should never have to do that. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
clang/llvm | lumiwa | FreeBSD General | 3 | 21st February 2013 12:30 AM |
Updating tint2 port/package | shep | OpenBSD Packages and Ports | 3 | 3rd February 2013 10:16 PM |
clang -v | lumiwa | FreeBSD General | 4 | 16th January 2013 03:26 PM |
FreeBSD FreeBSD 10 will be using Clang instead of GCC | J65nko | News | 0 | 15th May 2012 09:10 PM |
LLVM Clang Vs gcc | aleunix | OpenBSD General | 8 | 22nd February 2012 10:24 AM |