From owner-freebsd-ports  Tue Feb  6  9:47:25 2001
Delivered-To: freebsd-ports@freebsd.org
Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1A97337B503; Tue,  6 Feb 2001 09:47:04 -0800 (PST)
Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112])
	by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f16Hkv803901;
	Tue, 6 Feb 2001 19:47:00 +0200
Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1])
	by vic.sabbo.net (8.11.2/8.9.3) with ESMTP id f16Hl1939559;
	Tue, 6 Feb 2001 19:47:01 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
Message-ID: <3A803884.467879D9@FreeBSD.org>
Date: Tue, 06 Feb 2001 19:46:45 +0200
From: Maxim Sobolev <sobomax@FreeBSD.org>
Organization: Vega International Capital
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: uk,ru,en
MIME-Version: 1.0
To: ade@FreeBSD.org
Cc: roberto@eurocontrol.fr, freebsd-ports@FreeBSD.org
Subject: Re: ports/24901: Problem with some threaded ports (e.g.gnomevfs)
References: <200102061730.f16HUxp60919@freefall.freebsd.org>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

ade@FreeBSD.org wrote:

> 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.

It seems that the following additional point is required in this case (from my
private conversation with PR author):
0. Update your sources to the latest version using cvsup and rebuild/reinstall
world (it seems that he somehow has a world from the point when libc_r changes
were comitted, but -pthread option had not been adjusted yet to link with libc
in addition to libc_r).

-Maxim



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