From owner-freebsd-questions@FreeBSD.ORG Tue Oct 30 13:42:40 2007 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 4501516A418 for ; Tue, 30 Oct 2007 13:42:40 +0000 (UTC) (envelope-from jeffd6635@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by mx1.freebsd.org (Postfix) with ESMTP id EC99713C48D for ; Tue, 30 Oct 2007 13:42:39 +0000 (UTC) (envelope-from jeffd6635@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1296255nzf for ; Tue, 30 Oct 2007 06:42:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=k+sTJhm8PV9eni6HVc87f4fq7UKwVuHHjkq71qAtA+M=; b=bEzj63sZwjsn55jotQ0iQUARaYKeSeU78SBj29PK3r4cm84CwVK5QPn93XAD1ntKIPDm3h68E5OXms6VFgtAKMS9NYWrRcPvNF0FMcy+XEmIne+sZE3BF7fxpihXMGk4MvXw2fSjzn9O7jdLd3h71KhRxxS9pumR+rnb3cjCtes= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=c62IHwVfr6LIt0OC5fP9vnvNTVc2sim+b+8/h4jmG7AmhUAO9j0lPqO9HX21iRFELwmjgU3jWNMSMAJFck6h6F4MLENwp+wwB3jc0sHJgzdlXdO0RAAqOHOeTrgmxzDzGaPwQcyb6WbuFo9+qATLHmLfT4h5GOT4RAQqRdwbCmI= Received: by 10.142.214.5 with SMTP id m5mr1624006wfg.1193751757374; Tue, 30 Oct 2007 06:42:37 -0700 (PDT) Received: by 10.142.233.21 with HTTP; Tue, 30 Oct 2007 06:42:37 -0700 (PDT) Message-ID: Date: Tue, 30 Oct 2007 06:42:37 -0700 From: "Jeff D" To: "Matthew Seaman" In-Reply-To: <4726EC3E.3000405@infracaninophile.co.uk> MIME-Version: 1.0 References: <4726EC3E.3000405@infracaninophile.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: Newby Question: What to do when one port can't recognize another port? 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: Tue, 30 Oct 2007 13:42:40 -0000 Matthew, On 10/30/07, Matthew Seaman wrote: > > This is a known problem with the apache22 port. At the moment it only > understands about Berkeley DB versions up to 4.4.x -- there's an open > ticket in the PR system which requests support for versions up to 4.6.x: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/116637 > > Until that gets fixed, use BDB 4.4.x instead. To make that the default > version on your system add this to /etc/make.conf: > > WITH_BDB_VER= 44 Thanks for pointing this out. I'd thought that the port system in Freebsd was assured to be internally consistent with all other stuff in the system by a central team (QA?). I didn't realize that each port was from a different person, and that the process could get held up for weeks or months. I guess your advice is what I should do. I'm a little nervous about undoing what's already been done, and think I might just start over with db44 to be safe. Knowing this now, I guess I should also make a list of the programs and versions I need, and check each & every one for problems before I start again. If something popular like the Apache Web Server has long standing unresolved issues like this, other programs may too. A friend is pushing me to use Ubunutu Linux instead, saying that stuff like this doesn't happen with it, but I'm not so convinced. After being 'sold' on the Freebsd ports, it's worth some more reading. Thanks. Regards, Jeff