Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2012 15:04:37 +0400
From:      Yuri Pankov <yuri.pankov@gmail.com>
To:        Volodymyr Kostyrko <c.kworr@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: what is a correct way to build ports with clang
Message-ID:  <20120111110437.GA1429@procyon.xvoid.org>
In-Reply-To: <4F0D6712.8070601@gmail.com>
References:  <4F0D6712.8070601@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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...


Yuri



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120111110437.GA1429>