From owner-freebsd-current@freebsd.org Fri Jun 23 23:12:15 2017 Return-Path: Delivered-To: freebsd-current@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 961ACD8C3FB for ; Fri, 23 Jun 2017 23:12:15 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.225]) (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 76D4F78482 for ; Fri, 23 Jun 2017 23:12:14 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:23199] helo=localhost) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 39/EE-01815-840AD495; Fri, 23 Jun 2017 23:12:08 +0000 Date: Fri, 23 Jun 2017 23:12:04 +0000 Message-ID: <39.EE.01815.840AD495@dnvrco-omsmta03> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Ports still broken by ino64? X-RR-Connecting-IP: 107.14.64.88:25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 23:12:15 -0000 I remember some ports on FreeBSD-current were rendered nonbuildable by the introduction of 64-bit inodes (ino64). What is the progress on resolving those snags? I haven't heard anything recently and was unable to find anything on wiki.freebsd.org. So how do I know the current status? I am particularly concerned with gcc5-aux and gcc6-aux which should be of concern because ports-mgmt/synth requires gcc6-aux as a dependency. There was never a BROKEN in any of these ports' Makefile. Tom