From owner-freebsd-current@FreeBSD.ORG Wed Jul 19 11:02:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6092516A61B for ; Wed, 19 Jul 2006 11:02:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E99C43D5A for ; Wed, 19 Jul 2006 11:01:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 7F19A46CAA; Wed, 19 Jul 2006 07:01:58 -0400 (EDT) Date: Wed, 19 Jul 2006 12:01:58 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Patrick Bowen In-Reply-To: <44BD7DD5.9030406@fastmail.fm> Message-ID: <20060719120037.S2059@fledge.watson.org> References: <44BADEC8.5030807@fastmail.fm> <86ejwkrh83.fsf@student.uni-magdeburg.de> <44BD7DD5.9030406@fastmail.fm> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Firefox on -current dumps core. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 11:02:10 -0000 On Tue, 18 Jul 2006, Patrick Bowen wrote: >>>> I recently upgraded a Gateway MX6121 from 6.1 stable to -current, >>>> following the canonical procedure in /usr/src/UPDATING, and now whenever >>>> I try to start firefox, it dumps a core file (segmentation fault). >>>> Firefox was compiled from source under 6.1. >>>> >>>> Should I have upgraded from 6.1 to -current, and /then/ start adding >>>> ports, or does that matter? >>> >>> When I upgraded about two weeks ago, a lot of programs dumped core. >>> Rebuilding fixed that. I didn't have these problems when I upgraded >>> before, not even from 6.0 to 7.0-current, just this last time. >> >> Because there are libraries whose version have not been bumped yet in 7.0. >> > > Understood. > > Here's my situation. I drive a truck, and the truck stops have wireless, but > no wired, and there's a secure login. So I have to have a working browser to > get on the web to do updates/upgrades. > > What would be the best way to avoid the "library" problem that caused the > cores? Upgrade all the packages from source before I cvsup to -current, > or...? > > Thanks for any pointers. In short, the only way to fix these problems is to rebuild all your ports in order that the installed ports match your library set and that all applications linked against old library versions are updated. Eventually, there will be a compat6x port that installs compatibility versions of libraries, but there are a number of open questions about how we want to approach that (due to library version interdependence) so the short term solution of upgrading everything (and specifically, building them from scratch) is the way to go. Robert N M Watson Computer Laboratory University of Cambridge