what is a correct way to build ports with clang

Yuri Pankov yuri.pankov at gmail.com
Wed Jan 11 11:13:27 UTC 2012


On Wed, Jan 11, 2012 at 03:04:37PM +0400, Yuri Pankov wrote:
> On Wed, Jan 11, 2012 at 12:40:18PM +0200, Volodymyr Kostyrko wrote:
> > Hi all.
> > 
> > I recently stumbled upon minor inconsistency when building misc/mc. The 
> > build goes well when CPP is unset or when CPP=clang -E, but fails when 
> > CPP=clang-cpp:
> > 
> > /tmp/ports/usr/ports/misc/mc/work/mc-4.7.5.5/config.log:
> > 
> > configure:23603: checking for slang.h
> > configure:23618: clang-cpp -ltermcap -I/usr/local/include 
> > -I/usr/include -L/usr/lib conftest.c
> > Stack dump:
> > 0.      Program arguments: clang-cpp -ltermcap -I/usr/local/include 
> > -I/usr/include -L/usr/lib conftest.c
> > 1.      Compilation construction
> > 2.      Building compilation actions
> > configure:23618: $? = 139
> > 
> > What is the correct way to build ports with clang? Wiki states that CPP 
> > should be set to clang-cpp for everyone however this doesn't work here.
> 
> This can be reduced to just `clang-cpp -l<anything>` and I guess it's a
> bug...

And it seems to be http://www.llvm.org/bugs/show_bug.cgi?id=11581.


Yuri


More information about the freebsd-questions mailing list