Date: Thu, 23 Nov 2017 22:07:36 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Chris H <bsd-lists@bsdforge.com> Cc: bob prohaska <fbsd@www.zefox.net>, "ports@freebsd.org>" <ports@freebsd.org>, freebsd-arm@freebsd.org Subject: Re: Dependencies satisfied, build stops anyway. Message-ID: <CAN6yY1unNAE5n-1e0dp9cyfR=5DFjxk_h2gMLrGB2CvgGZCxCA@mail.gmail.com> In-Reply-To: <2ab2735988a2d2dee23f00834dee872b@udns.ultimatedns.net> References: <20171123051228.GA64807@www.zefox.net> <2ab2735988a2d2dee23f00834dee872b@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 22, 2017 at 9:23 PM, Chris H <bsd-lists@bsdforge.com> wrote: > On Wed, 22 Nov 2017 21:12:28 -0800 "bob prohaska" <fbsd@www.zefox.net> > said > > On Wed, Nov 22, 2017 at 08:32:53PM -0800, Kevin Oberman wrote: >> > > Stale ports SHOULD not be an issue. Normally old ports are updated >> > automatically. It is important that your ports tree is consistent and, >> > usually that it is current. Assuming yours is, the only issue is the >> > oddball case like this one. You won't hit them often. Usually it is >> when a >> > file that is tested for is missing. Usually a library. pkgdb says that >> the >> > port is installed, but the make looks for the actual library and >> triggers >> > an install, as opposed to a reinstall, when it is not found. Unled this >> > systm has been massively mangled, it is a very unusual development, at >> > least in my experience. >> > -- >> >> Aye, there's the rub 8-) >> >> Some time ago I accidentally destroyed most of /usr and ended up >> reconstructing it from a recent snapshot. Since buildworld and >> buildkernel seemed to work in /usr/src, I thought /usr/ports would >> be likewise recovered after a fresh checkout. >> >> For now I've set >> FORCE_PKG_REGISTER=yes in /etc/src.conf and that seems to allow make to >> proceed without >> interruptions for dns/bind910, but I gather that's not a long-term >> fix. >> > I think you might have been better off going with the suggested > cd /offending/port > make deinstall > make reinstall > > The choice to pollute your environment with FORCE_PKG_REGISTER > will simply compound the problem you're already experiencing. :( > Just saying. > > In the end, you're probably going need to decide on a revision, > and check it out for both src && ports. Then perform a fresh > build(world/kernel) && install world/kernel. Else you'll be > fighting this and other woes for eternity. > > I'm only saying all this in an effort to help. :) > > All the best, and best of luck. :) > > --Chris > > > >> Thanks very much! >> >> bob prohask > > Ouch! Yes, you have a mess. There is no requirement that ports and src be in sync. If you are running any supported version of FreeBSD (10.4, 11.1, 10-STABLE, or 11-STABLE) or CURRENT, you should be fine with updating your ports tree. Then you can create a list of installed ports, delete all ports, and then re-install from the list. If you use portmaster, the man page has a fairly simple list of steps that can let you do that job. If you rebuild everything from ports, it will take a while. I've done this for well over 1000 ports and it had taken a couple of days. -- 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?CAN6yY1unNAE5n-1e0dp9cyfR=5DFjxk_h2gMLrGB2CvgGZCxCA>