From owner-freebsd-ports@FreeBSD.ORG Mon Aug 11 05:13:13 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D0A737B401 for ; Mon, 11 Aug 2003 05:13:13 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id B524D43FB1 for ; Mon, 11 Aug 2003 05:13:11 -0700 (PDT) (envelope-from rooneg@electricjellyfish.net) Received: (qmail 58765 invoked from network); 11 Aug 2003 12:13:10 -0000 Received: from unknown (HELO electricjellyfish.net) (66.9.75.43) by relay.pair.com with SMTP; 11 Aug 2003 12:13:10 -0000 X-pair-Authenticated: 66.9.75.43 Message-ID: <3F378856.1010601@electricjellyfish.net> Date: Mon, 11 Aug 2003 08:13:10 -0400 From: Garrett Rooney User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030701 Thunderbird/0.1a X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Collins-Sussman References: <3F371A07.8000604@daniel.stefan.haischt.name> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org cc: bmah@freebsd.org cc: users@subversion.tigris.org cc: "Daniel S. Haischt" Subject: Re: [PYTHON-BINDINGS] compiling FreeBSD port with svn bindings X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 12:13:13 -0000 Ben Collins-Sussman wrote: > "Daniel S. Haischt" writes: > > >>/usr/local/lib/apache2/libapr-0.so: undefined reference to `pthread_create' >> >>can you give me any pointers what is going wrong or how to >>compile subversion with the --with-swig option set to yes? > > > The swig-py bindings require APR threads, but on FreeBSD, APR disables > threads by default. You need to make sure APR is configured with the > --enable-threads option. Actually, gstein, jerenkrantz, and myself discussed this at OSCON, and came up with a way to make it work without apr threads, something about requiring us to pick up the python interpreter lock when entering subversion code if we don't have threads turned on in apr (since all subversion calls are potentially not thread safe in that case). I don't think anyone has gotten around to implementing this, but it seems like this problem can be made to go away in the near future. -garrett