From owner-freebsd-ports@freebsd.org Thu Jun 1 00:24:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4E88BEE020 for ; Thu, 1 Jun 2017 00:24:28 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B1A73726B6 for ; Thu, 1 Jun 2017 00:24:28 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from [74.134.208.22] ([74.134.208.22:47586] helo=localhost) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 70/5D-01815-5BE5F295; Thu, 01 Jun 2017 00:24:21 +0000 Date: Thu, 01 Jun 2017 00:23:59 +0000 Message-ID: <70.5D.01815.5BE5F295@dnvrco-omsmta03> From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: Re: The future of portmaster References: <201705301351.v4UDpHwY048949@mech-as222.men.bris.ac.uk> <9FEDBFCE-27D1-432B-926B-7BF401AD7B19@adamw.org> <589B133C-0175-4DD2-8847-5A3E0E697B36@dsl-only.net> <1496236662.1196.1.camel@mailman-hosting.com> X-RR-Connecting-IP: 107.14.64.88:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 00:24:28 -0000 > On Wed, 2017-05-31 at 12:47 +0000, Gerard Seibert wrote: > > I would just like a clarification here. For the record, synth is > > broken > > on FreeBSD-11 and above with amd64. Is that correct? > My understanding was that the breakage is in gcc6-aux on 12-CURRENT > with 64 bit inodes. > I may be wrong... > Jim Ohlstein That was my understanding too, both gcc5-aux and gcc6-aux being broken on CURRENT with 64-bit inodes. Now I feel like I can upgrade with 11.0-STABLE but not CURRENT. My recent CURRENT installation seems too unstable to use as a build host. I would rebuild 11.0-STABLE first and later use that as a host to rebuild CURRENT. I would want gcc(5 or 6)-aux not only for synth but also (gcc5) to try to cross-compile Haiku and (gcc5 or 6) to try to cross-compile a Linux toolchain. I would also want an updated FreeBSD system that ports would support as opposed to something like FreeBSD amelia 11.0-CURRENT FreeBSD 11.0-CURRENT #10 r294248: Mon Jan 18 11:28:40 UTC 2016 root@amelia:/usr/obj/usr/src/sys/SANDY11NC amd64 Regarding portmaster, when something on which a lot of other ports depend is upgraded, such as a major version update of png, it takes many runs of portmaster before everything is successfully updated. Tom