Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Nov 2017 21:23:56 -0800
From:      "Chris H" <bsd-lists@BSDforge.com>
To:        "bob prohaska" <fbsd@www.zefox.net>
Cc:        "ports@freebsd.org>" <ports@FreeBSD.org>, <freebsd-arm@freebsd.org>, "Kevin Oberman" <rkoberman@gmail.com>
Subject:   Re: Dependencies satisfied, build stops anyway.
Message-ID:  <2ab2735988a2d2dee23f00834dee872b@udns.ultimatedns.net>
In-Reply-To: <20171123051228.GA64807@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 Nov 2017 21:12:28 -0800 "bob prohaska" <fbsd@www=2Ezefox=2Enet> said

> On Wed, Nov 22, 2017 at 08:32:53PM -0800, Kevin Oberman wrote:
> >=20
> > Stale ports SHOULD not be an issue=2E Normally old ports are updated
> > automatically=2E It is important that your ports tree is consistent and,
> > usually that it is current=2E Assuming yours is, the only issue is the
> > oddball case like this one=2E You won't hit them often=2E Usually it is whe=
n a
> > file that is tested for is missing=2E Usually a library=2E pkgdb says that =
the
> > port is installed, but the make looks for the actual library and trigge=
rs
> > an install, as opposed to a reinstall, when it is not found=2E Unled this
> > systm has been massively mangled, it is a very unusual development, at
> > least in my experience=2E
> > --
>=20
> Aye, there's the rub 8-)
>=20
> Some time ago I accidentally destroyed most of /usr and ended up
> reconstructing it from a recent snapshot=2E Since buildworld and
> buildkernel seemed to work in /usr/src, I thought /usr/ports would
> be likewise recovered after a fresh checkout=2E
>=20
> For now I've set
> FORCE_PKG_REGISTER=3Dyes=20
> in /etc/src=2Econf and that seems to allow make to proceed without
> interruptions for dns/bind910, but I gather that's not a long-term
> fix=2E
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=2E :(
Just saying=2E

In the end, you're probably going need to decide on a revision,
and check it out for both src && ports=2E Then perform a fresh
build(world/kernel) && install world/kernel=2E Else you'll be
fighting  this and other woes for eternity=2E

I'm only saying all this in an effort to help=2E :)

All the best, and best of luck=2E :)

--Chris

>=20
> Thanks very much!
>=20
> bob prohaska
>





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ab2735988a2d2dee23f00834dee872b>