From owner-freebsd-ports  Tue Feb  6  9:31:16 2001
Delivered-To: freebsd-ports@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id D71EA37B491; Tue,  6 Feb 2001 09:30:59 -0800 (PST)
Received: (from ade@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f16HUxp60919;
	Tue, 6 Feb 2001 09:30:59 -0800 (PST)
	(envelope-from ade)
Date: Tue, 6 Feb 2001 09:30:59 -0800 (PST)
From: <ade@FreeBSD.org>
Message-Id: <200102061730.f16HUxp60919@freefall.freebsd.org>
To: roberto@eurocontrol.fr, ade@FreeBSD.org,
	freebsd-ports@FreeBSD.org
Subject: Re: ports/24901: Problem with some threaded ports (e.g.gnomevfs)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Problem with some threaded ports (e.g.gnomevfs)

State-Changed-From-To: open->closed
State-Changed-By: ade
State-Changed-When: Tue Feb 6 09:26:00 PST 2001
State-Changed-Why: 
The solution, because so damn many things were screwed up with the
threading changes in -current, is simple.

1.  Build a post-apocalypse -current
2.  backup configuration files
3.  rm -rf /var/db/pkg/* /usr/local/* /usr/X11R6/* (plus elsewhere
    if you play with PREFIX).
4.  Rebuild every single port from source (do not use the 5.x packages)

When -current stabilizes enough that these kind of massive and far-reaching
userland changes quieten down, then it'll be easier to go through ports/
and see if there are any remaining friendly fire casualties.

http://www.freebsd.org/cgi/query-pr.cgi?pr=24901


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message