From owner-freebsd-current@FreeBSD.ORG Tue Jun 4 19:53:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DA48AA17 for ; Tue, 4 Jun 2013 19:53:59 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id A04DB1940 for ; Tue, 4 Jun 2013 19:53:59 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::4521:e4f7:9b8a:a981] (unknown [IPv6:2001:7b8:3a7:0:4521:e4f7:9b8a:a981]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 015865C44; Tue, 4 Jun 2013 21:53:56 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Can't compile databases/py-sqlite3 From: Dimitry Andric In-Reply-To: Date: Tue, 4 Jun 2013 21:53:57 +0200 Content-Transfer-Encoding: 7bit Message-Id: References: To: Walter Hurry X-Mailer: Apple Mail (2.1503) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 04 Jun 2013 19:53:59 -0000 On Jun 4, 2013, at 21:15, Walter Hurry wrote: > I'm running 10.0-CORRENT on amd64. Ports and source are both up to date. > > When I try a 'make install' in /usr/ports/databases/py-sqlite3 I get this > very early on: > > ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py- > sqlite3/work/Python-2.7.5/configure > running config > : /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/ > internal/arena.h:547: Failed assertion: "binind < NBINS || binind == > BININD_INVALID" > *** Signal 6 > > Stop. > make: stopped in /usr/ports/databases/py-sqlite3 > > I'm afraid this binind business doesn't mean much to me. Is there > anything I can do? Please try the patch from this very recent post (on this very list ;-): http://lists.freebsd.org/pipermail/freebsd-current/2013-June/042230.html