From owner-freebsd-current@freebsd.org Sat Jun 24 04:17:09 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 BD4A3D96731 for ; Sat, 24 Jun 2017 04:17:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D41381E57 for ; Sat, 24 Jun 2017 04:17:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-pg0-x22a.google.com with SMTP id u62so28417245pgb.3 for ; Fri, 23 Jun 2017 21:17:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aTbbmmD0qKVX397/7yIWNHo7wJ58vrGwW6Jx9boc0Aw=; b=b8qjh6IFX1TYrsBfRrtNFgEannxNZNmHysV7wkCLECsBYoo8o9uvrVJQ2GqE+tbeHZ EQNAIFNTiaXp4B0VGyUB31AwkdAgYQvW7u0sLH8qPcuWfgPGxE5fg+hirj0AC+5exOfI 8fci0PodhZGQuX536AZJdFG3GD5qbReHWqBU0CZ9bhUvhExembBzx2A1BFi4iM0HsAqQ KEvxxf0rKrf7PR4IkBOGDU5KmJTpIhOUUCjS590KRtJAnqUl4qNGRWSo3aHfd0GudxjL g2hu6mxKvLD7QCDRnz5/1LKH/IYTk9SHTUEfXeoyJ+kgZ+Xu3ncWqRxwU3wwQMTZRQ5K lLPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=aTbbmmD0qKVX397/7yIWNHo7wJ58vrGwW6Jx9boc0Aw=; b=qOiGetDqN8sxIlApY72WjHfvNGRkSvMdVKlVxBNQiFH+1y2VC3FUWQWYnA+1D7NcnT FVuSuhqVnip4ShA0CDlC6yGcLrke3p0vvg4vUKuwZFxRboma2NouTzY4Vx2w1gizN0Th 929GcyIzs/Yp6LDWjeCrAtZHIrPgHQ44xqyi76zJn/xIMwNEvM96eMu32tj4Tnf0/swq 4Ileox1uh3i87Gly5zJX+3ZHS9t4R8F1OxPP0J+lvoRemeMVZphF53/yjR7KoVpQvvAJ 6W3+hNvWn+E9/JutGXZU753tjYUgj82TbC7WvXOLva7o/YCtDF7+N9YfLxKpvNuk8pNZ MeOg== X-Gm-Message-State: AKS2vOx4tTaKB7/VoL1lZqM03CvZt5zl6GZXJWCff/v+uPuXPFABY2kb o0hhn8sI1GGk9aIcWlbxJDbCeENtpo1x4GE= X-Received: by 10.98.68.2 with SMTP id r2mr11608590pfa.190.1498277829149; Fri, 23 Jun 2017 21:17:09 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.100.140.202 with HTTP; Fri, 23 Jun 2017 21:17:08 -0700 (PDT) In-Reply-To: <78.25.03057.F5ADD495@dnvrco-omsmta02> References: <78.25.03057.F5ADD495@dnvrco-omsmta02> From: Kevin Oberman Date: Fri, 23 Jun 2017 21:17:08 -0700 X-Google-Sender-Auth: FGfJ3eWU8RRLxci6pYQiZdSP6Bk Message-ID: Subject: Re: Ports still broken by ino64? To: Thomas Mueller Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Sat, 24 Jun 2017 04:17:09 -0000 On Fri, Jun 23, 2017 at 8:19 PM, Thomas Mueller wrote: > On Fri, Jun 23, 2017 at 4:12 PM, Thomas Mueller > wrote: > > > > 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 > > > > IIRC, there was no general issue with building ports, though a few may > have > > needed a fix. It was that packages built after the change were not > > available and older binaries would not work. I believe that the issue > went > > away as soon as a new package build was completed. This took longer than > > usual as ALL packages had to be re-built, not just those which had been > > updated since the last build. > > > Kevin Oberman, Part time kid herder and retired Network Engineer > > So I guess I could update my FreeBSD-current installation, building from > 11-stable host, and try again to build synth? > > But all the dependencies that build successfully and installed before the > system crash would have to be rebuilt from the start. > > It will take some time before I get to it, with an 11.1-BETA2 installation > being built up and some NetBSD installations being updated (not easy, > problems are such as to dissuade me from tryimg to use pkgsrc on FreeBSD). > > I know that any old FreeBSD-current installation from January 2016 or > August 2015 must not be touched lest all or nearly all packages be rendered > nonfunctional due to shared libraries out of sync, not to mention ino64. > > Upgrade after FreeBSD 11.1-STABLE/BETA2 installation is built up and ready > to take over. > > One thing that might put rebuilding FreeBSD-current to a higher priority > would be an update to > $SRC_BASE/sys/dev/re/if_re.c > > Tom > Maybe not, but I think so. synth(8) requires the ada compiler which means lang/gcc6-aux or lang/gcc5-aux and those DID require work to install on ino64. I believe that this is now resolved, but I would seriously consider simply installing synth from the package. It has no run or lib depends, so installing the package is risk-free. synth is the only package I install on my development system,though I do consider installing chromium and libreoffice from packages now and then... like every time I have to rebuild either. (libreoffice is awaiting for a rebuild right now. Maybe tomorrow. I built Chromium yesterday.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683