From owner-freebsd-ports@FreeBSD.ORG Wed Jun 12 04:12:31 2013 Return-Path: Delivered-To: ports@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1033) id D19CF534; Wed, 12 Jun 2013 04:12:31 +0000 (UTC) Date: Wed, 12 Jun 2013 04:12:31 +0000 From: Alexey Dokuchaev To: Martin Wilke Subject: Re: [CFH] FreeBSD 10 and ports Message-ID: <20130612041231.GA97924@FreeBSD.org> References: <249D4A03-A62A-4033-9757-AF308D4422FF@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <249D4A03-A62A-4033-9757-AF308D4422FF@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "ports@freebsd.org Ports" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jun 2013 04:12:31 -0000 On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote: > As we all know FreeBSD 10 brings a new compiler along, and for that we > need > to get ports on the right track. I have done several exp-runs on > the current src and we still have a lot of fallouts. We would like to > ask you to have a look [1] at the failed ports and help to fix them. As a side note, I encourage people first try to figure out what's upsetting Clang and appropriately fix it, rather than marking port as GCC-only, and send patches upstream once you're happy with them. This is less true for warnings, (given that they can be easily disabled, yet just as easy to fix), so my call goes mostly towards real errors. ./danfe