Date: Fri, 23 Jun 2017 18:28:19 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Thomas Mueller <mueller6722@twc.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Ports still broken by ino64? Message-ID: <CAN6yY1uQ6w2CkdM6M2wkOiYQd5-X6HqAsVph7RYCnTKn2mXQeA@mail.gmail.com> In-Reply-To: <39.EE.01815.840AD495@dnvrco-omsmta03> References: <39.EE.01815.840AD495@dnvrco-omsmta03>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 23, 2017 at 4:12 PM, Thomas Mueller <mueller6722@twc.com> 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 E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uQ6w2CkdM6M2wkOiYQd5-X6HqAsVph7RYCnTKn2mXQeA>