From owner-freebsd-ports@FreeBSD.ORG Sun May 2 07:35:24 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2F14106566B for ; Sun, 2 May 2010 07:35:24 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id AE0178FC0A for ; Sun, 2 May 2010 07:35:24 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o427PN9V043039; Sun, 2 May 2010 00:25:23 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4BDD28E2.8010201@rawbw.com> Date: Sun, 02 May 2010 00:25:22 -0700 From: Yuri User-Agent: Thunderbird 2.0.0.24 (X11/20100331) MIME-Version: 1.0 To: =?UTF-8?B?QW5kcml1cyBNb3JrxatuYXM=?= References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: GSoC: Making ports work with clang X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 May 2010 07:35:24 -0000 Andrius Morkūnas wrote: > Hi, > > I'm Andrius Morkūnas from Lithuania. My Summer of Code proposal was > accepted > this year and be working on my project, which is to make clang and > ports to > be friendly with each other. > My main goals are: > * Create an easy way to set ports compiler to either clang or gcc (and > no, > CC=clang is not a good way to do that). > * Write a tool to detect common problems with individual ports not > respecting > environment variables like CC/CXX or doing other horrible things > that break > compilation with clang. > * Make Gnome, KDE, Xorg and other widely used things to work with clang. Having tried clang++ I have a feeling that it's not quite ready to be a generic c++ compiler. It crashes a lot, fails on many quite simple c++ patterns. Very immature. Don't you feel it's too early to start project like you are going to given the state of clang with c++? You will just keep stumbling upon various problems with various ports and maybe will make 30% of c++ ports build with it at best. Yuri