From owner-freebsd-ports@FreeBSD.ORG Tue Jun 11 19:33:16 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 918C39B; Tue, 11 Jun 2013 19:33:16 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 02F6F1874; Tue, 11 Jun 2013 19:33:15 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id c10so4348183wiw.17 for ; Tue, 11 Jun 2013 12:33:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=mt/BVD2y3v2QvF/FuTy7UuKxZ7eA9Cb8Q+HfraYCzTs=; b=aaFO2rrIfa5n7sIsD//Tji2jFTmQ9pizt+NDPmCkG+MByNGgdrS/h4Y5bEUNqNJQOU nX5Q9u/kDf1V3vLTM7PDrJzU0btdF+AxOXEKjt0XW8YWtvPcvCnQtYjRy9WKOmLFlWNx efYYz6oT4IzwXBNCSld52uLeLEUHaubq/30WeE7QGzyzUvocNrajns2MQQAYlvebr0D5 uY36oParPTmCMRexmtO3QJrhK7UK5EkzQAPdei8a/ezAFSJJz5MnLPsTUkkrlQ0oPp3n XdfdwEU7Ujfu6dseDPXmYaGhS+na9ULS12o4BgZYoGcKHyYFM/cNzCOPCw+z5cIAmuSk cQwQ== X-Received: by 10.194.242.229 with SMTP id wt5mr9452075wjc.36.1370979195066; Tue, 11 Jun 2013 12:33:15 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id ev19sm19853490wid.2.2013.06.11.12.33.13 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 11 Jun 2013 12:33:14 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 11 Jun 2013 21:33:12 +0200 From: Baptiste Daroussin To: Konstantin Belousov Subject: Re: [CFH] FreeBSD 10 and ports Message-ID: <20130611193311.GA84600@ithaqua.etoilebsd.net> References: <249D4A03-A62A-4033-9757-AF308D4422FF@FreeBSD.org> <20130611192156.GU3047@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <20130611192156.GU3047@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "ports@freebsd.org Ports" , Martin Wilke 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: Tue, 11 Jun 2013 19:33:16 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 11, 2013 at 10:21:56PM +0300, Konstantin Belousov wrote: > On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote: > >=20 > > Dear All, > >=20 > > 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 hav= e a lot of fallouts. We > > would like to ask you to have a look [1] at the failed ports and help t= o fix them. We will start this week > > an i386 exp-run to see how the status is. > >=20 > > Thanks for your time. > >=20 > > - Martin on behalf of portmgr > >=20 > > [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/ >=20 > Didn't a sort of consensus when switching to clang for base was > discussed, was that ports would start use a port-provided version of gcc > ? The adoption of the ports gcc was stalled due to the unability to make > exp-runs, AFAIK. >=20 > What you are proposing is de-facto forking the whole open-source code > base. This cannot work, and in fact steals the FreeBSD resources for > something which has absolutely no relevance for FreeBSD project. >=20 > Ports should not be forced to use clang, either a ports gcc work > should be finished, or cc in HEAD switched back to gcc. This is > de-facto blocker for the 10.0. having a "ports compiler" means having a full toolchain for ports, which has lots of collision with the toolchain in base system. As far as I know, ther= e was no consensus at all, but some of us are working on a ports toolchain to see= how it goes. All the problem (most at least) we find with clang from base are the same we will have to fight with with recent gcc, plus recent gcc brings recent binu= tils which will give us even more headache (the same we will have to face one day with mclinked). We are close to have the full ports tree working working on 10 may that be = by directly support clang or using the USE_GCC macros allowing to choose a gcc= from ports if needed. regards, Bapt --J/dobhs11T7y2rNN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlG3e3cACgkQ8kTtMUmk6ExzogCfaa3/85XLP0T54s+AUx3s0/we bRYAnRE/2c0/VQ55N48FdmAmLGsr47QF =RYPg -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN--