From owner-freebsd-questions@FreeBSD.ORG Thu Mar 17 04:47:42 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D901816A4CE; Thu, 17 Mar 2005 04:47:42 +0000 (GMT) Received: from MXR-7.estpak.ee (mail.hot.ee [194.126.101.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 783E743D55; Thu, 17 Mar 2005 04:47:41 +0000 (GMT) (envelope-from toomas.aas@raad.tartu.ee) Received: from [217.159.164.183] (217-159-164-183-dsl.trt.estpak.ee [217.159.164.183]) by MXR-7.estpak.ee (Postfix) with ESMTP id 8F53AB6C73; Thu, 17 Mar 2005 06:47:39 +0200 (EET) Message-ID: <42390B81.4080009@raad.tartu.ee> Date: Thu, 17 Mar 2005 06:45:53 +0200 From: Toomas Aas User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <42388091.5060103@raad.tartu.ee> <20050316200949.GF91771@hub.freebsd.org> In-Reply-To: <20050316200949.GF91771@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at hot.ee cc: questions@FreeBSD.ORG Subject: Re: Which ports use C++? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2005 04:47:43 -0000 Kris Kennaway wrote: > On Wed, Mar 16, 2005 at 08:53:05PM +0200, Toomas Aas wrote: > >>Or should I more or less expect that I need to rebuild *all* the ports >>anyway? > > That's best; there are other incompatibilities that are there when you > have old (compiled on 5.2) versions of a library and you try and > compile new software against them on 5.3. OK. But just to make sure I understand it right - does this mean that if I upgrade to 5.3, then those ports that depend on some incompatible library or are written in C++ do not work until they are recompiled? I'm aware that some of the library upgrades can be overcome with /etc/libmap.conf, but apparently this doesn't get it all.