Date: Tue, 8 Sep 2009 01:49:07 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: Error compiling KDE 3 Message-ID: <20090908014907.271dd347@gumby.homeunix.com> In-Reply-To: <d356c5630909021808w4a07ffddyf1fd809188e1de89@mail.gmail.com> References: <beaf3aa50909021226p5e834b6en1d640727c4be3057@mail.gmail.com> <20090902160336.70d2a4c4@scorpio.seibercom.net> <d356c5630909021808w4a07ffddyf1fd809188e1de89@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Sep 2009 20:08:26 -0500 Andrew Gould <andrewlylegould@gmail.com> wrote: > On Wed, Sep 2, 2009 at 3:03 PM, Jerry<gesbbb@yahoo.com> wrote: > > cd /usr/ports/security/gnutls > > make deinstall && make reinstall && make distclean > > cd - > > make install > > > > -- > > Jerry > > gesbbb@yahoo.com > > > > The package list may have changed between version 2.6.4 and 2.8.3. I > would recommend replacing "make deinstall", above, with: > > pkg_delete gnutls-2.6.4 There's no significant difference between "make deinstall" and pkg_delete - the last time I checked there was only one port that didn't use the default "make deinstall" target, which calls "pkg_delete -f". Usually this kind of thing happens because files moved between ports, and the best thing is to remove all of the affected ports before upgrading. Normally there's an UPDATING entry advising this. The FORCE_PKG_REGISTER method is a bit of cludge, but I gather it also works for this kind of build problem. I guess it allows a repeat install when a package has lost files due to a transient conflict.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090908014907.271dd347>