From owner-freebsd-ports@FreeBSD.ORG Mon May 3 11:15:38 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 C96661065673; Mon, 3 May 2010 11:15:38 +0000 (UTC) (envelope-from cbergstrom@pathscale.com) Received: from mail-pz0-f201.google.com (mail-pz0-f201.google.com [209.85.222.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9D3468FC12; Mon, 3 May 2010 11:15:38 +0000 (UTC) Received: by pzk39 with SMTP id 39so1213214pzk.7 for ; Mon, 03 May 2010 04:15:32 -0700 (PDT) Received: by 10.143.177.5 with SMTP id e5mr94827wfp.304.1272885331907; Mon, 03 May 2010 04:15:31 -0700 (PDT) Received: from [192.168.1.33] (ppp-58-8-182-179.revip2.asianet.co.th [58.8.182.179]) by mx.google.com with ESMTPS id 21sm4582771pzk.0.2010.05.03.04.15.26 (version=SSLv3 cipher=RC4-MD5); Mon, 03 May 2010 04:15:31 -0700 (PDT) Message-ID: <4BDEB154.8060104@pathscale.com> Date: Mon, 03 May 2010 18:19:48 +0700 From: =?UTF-8?B?IkMuIEJlcmdzdHLDtm0i?= User-Agent: Thunderbird 2.0.0.22 (X11/20090909) MIME-Version: 1.0 To: Dimitry Andric References: <4BDD28E2.8010201@rawbw.com> <20100503092213.GA1294@straylight.m.ringlet.net> <4BDEA78F.90303@pathscale.com> <4BDEA926.4030900@andric.com> In-Reply-To: <4BDEA926.4030900@andric.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: =?UTF-8?B?dXMgTW9ya8WrbmFz?= , freebsd-hackers@freebsd.org, =?UTF-8?B?QW5kcmk=?=, Peter Pentchev , freebsd-ports@freebsd.org, yuri@rawbw.com Subject: Re: GSoC: Making ports work with clang X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2010 11:15:38 -0000 Dimitry Andric wrote: > On 2010-05-03 12:38, "C. Bergström" wrote: > >> What's really the goal here? What problem are you working to solve? >> May I humbly say that building software with a different compiler in >> itself doesn't really accomplish anything. >> > > Of course it does. It forces you to make your software portable. > and your point is? Are you trying to say that s/building/porting/ between compilers is going to magically make the software (have less bugs, more performance or better robustness) Porting could be a means-to-an-end, but still it's not an end goal.. I'm digging at what's the end goal.. After it's all ported what magically happens?