From owner-freebsd-questions@FreeBSD.ORG Thu Dec 31 02:24:03 2009 Return-Path: Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CA7D106568F for ; Thu, 31 Dec 2009 02:24:03 +0000 (UTC) (envelope-from doug@safeport.com) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by mx1.freebsd.org (Postfix) with ESMTP id EDE168FC08 for ; Thu, 31 Dec 2009 02:24:02 +0000 (UTC) Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.3/8.14.3) with ESMTP id nBV2O2Pt012927; Wed, 30 Dec 2009 21:24:02 -0500 (EST) (envelope-from doug@safeport.com) Received: from localhost (doug@localhost) by fledge.watson.org (8.14.3/8.14.3/Submit) with ESMTP id nBV2O2mo012924; Wed, 30 Dec 2009 21:24:02 -0500 (EST) (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Wed, 30 Dec 2009 21:24:02 -0500 (EST) From: doug@safeport.com X-X-Sender: doug@fledge.watson.org To: Warren Block In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Wed, 30 Dec 2009 21:24:02 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG Subject: Re: xorg-7.4_2 error (was xorg 7.4 questions) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2009 02:24:03 -0000 On Wed, 30 Dec 2009, Warren Block wrote: > On Wed, 30 Dec 2009, doug@safeport.com wrote: > >>> After updating ports, 'portsdb -Fu' and 'portversion -vL=' will show >>> what's outdated. (That's with portupgrade installed. Some would have you >>> believe it's second in evil only to HAL. Maybe true, but it works.) >>> >>> And then 'portupgrade -r portname' (or 'portupgrade -ar', if you like) >>> should upgrade the outdated stuff and everything that depends on it. And >>> -P or -PP might help by retrieving packages, although I haven't tried that >>> in years. >> >> This includes libc? man 2 libc > > Doh, I was thinking of ports, not system. Some ports have code to check for > system version requirements, and I'd expect packages to do the same thing. > But they're moving targets, and developers and porters can't check all the > combinations. First building the system does indeed solve all xorg package problems. Second I am not sure I agree with your statement. I think the answer is relatively easy: (1) build packages against the base release, or, (2) document the problem, or lastly (3) have the port management tools check for this. While I am not sure if (3) is possible, I am pretty sure (2) is. Anyway X and its successor Xorg is at once the great leveler and I have learned more about FreeBSD getting my Desktops going than any other single activity. I appreciate all the time you spent leading me to the solution. Bouncing thoughts and ideas with you was most helpful. I wanted to post my original comment and this to make explicit that a version 7 package will not necessarily work on a 7.2 system. I certainly do not have the knowledge to know what system libraries a port is built on. This was actually quite easy to find because of the error. If there is no error you are left doing a ktrace or something. By the way have gotten the error and figuring out that libc was involved, I did not understand the implication, I had help there.