From owner-freebsd-questions@freebsd.org Sat Apr 23 15:42:03 2016 Return-Path: Delivered-To: freebsd-questions@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 1B507B19CE6 for ; Sat, 23 Apr 2016 15:42:03 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S5.hotmail.com (blu004-omc4s5.hotmail.com [65.55.111.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D073F1714 for ; Sat, 23 Apr 2016 15:42:02 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP13 ([65.55.111.136]) by BLU004-OMC4S5.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 23 Apr 2016 08:40:54 -0700 X-TMN: [f+rkY+Uba5r9ImMf8ueZoDvwyRO3/Te1] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Sat, 23 Apr 2016 11:40:52 -0400 From: Carmel To: freebsd-questions@freebsd.org Subject: Re: Sane way to resolve potential conflicts in the system In-Reply-To: <20160423162910.7cd2ede2@curlew.lan> References: <20160423162910.7cd2ede2@curlew.lan> Organization: Seibercom NET X-Mailer: Claws Mail 3.13.2-dirty (GTK+ 2.24.28; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2016 15:40:54.0486 (UTC) FILETIME=[85ACEF60:01D19D76] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2016 15:42:03 -0000 On Sat, 23 Apr 2016 16:29:10 +0100, Mike Clarke stated: >On Sat, 23 Apr 2016 15:00:10 +0300 >Odhiambo Washington wrote: > >> I believe that explains it. I should plan a portupgrade -a one of >> these days I suppose. > >You also need to make sure your ports tree is up to date first. Try doing a "portupgrade -af". That should ensure all of your ports are linked to the correct libraries. -- Carmel