[Bug 118135] kdevelop 3.3 doesn't compile on Slackware current (10.2)

[Alexander Dymo]

On Monday 12 December 2005 03:51, Matt Rogers wrote:
> do not revive our copy of bdb. This is system specific to slackware users.
> they need to specify
> --with-db-includedir=/usr/include/db4
> or adjust their /usr/include/db.h symlinks to point to the db 4 version of
> the header.
Do we have the guarantee that all versions of bdb work with our code
completion engine? I know it used to crash under certain conditions.
Have that been fixed?


>From "Matt Rogers <mattr"@kde.org Mon Dec 12 21:59:41 2005
Received: from mout1.mail.vrmd.de ([81.28.224.19])
	by barney.cs.uni-potsdam.de with esmtp (Exim 3.36 #2)
	id 1Elulm-0002MV-00
	for kdevelop-devel at barney.cs.uni-potsdam.de; Mon, 12 Dec 2005 21:59:39 +0100
Received: from [81.28.224.26] (helo=mail.variomedia.de)
	by mout1.mail.vrmd.de with esmtpa (Exim 4.43)
	id 1Eluln-0005UQ-Kf
	for kdevelop-devel at barney.cs.uni-potsdam.de; Mon, 12 Dec 2005 21:59:39 +0100
Received: from smtp103.sbc.mail.mud.yahoo.com ([68.142.198.202])
	by mail.variomedia.de with smtp (Exim 4.43)
	id 1Elulk-00039x-Is
	for kdevelop-devel at kdevelop.org; Mon, 12 Dec 2005 21:59:36 +0100
Received: (qmail 51112 invoked from network); 12 Dec 2005 20:33:12 -0000
Received: from unknown (HELO localhost) (mgrogers at sbcglobal.net@70.136.103.236 with login)
  by smtp103.sbc.mail.mud.yahoo.com with SMTP; 12 Dec 2005 20:33:12 -0000
From: Matt Rogers <mattr at kde.org>
To: kdevelop-devel at kdevelop.org
Subject: Re: [Bug 118135] kdevelop 3.3 doesn't compile on Slackware current (10.2)
Message-ID: <20051212204529.GA7115 at shocker.internal>
References: <20051211212008.28488.qmail at ktown.kde.org> <200512120306.34589.adymo at mksat.net> <200512111951.14639.mattr at kde.org> <200512122009.25158.adymo at mksat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200512122009.25158.adymo at mksat.net>
User-Agent: Mutt/1.4.2.1i
Sender: kdevelop-devel-admin at barney.cs.uni-potsdam.de
Errors-To: kdevelop-devel-admin at barney.cs.uni-potsdam.de
X-BeenThere: kdevelop-devel at barney.cs.uni-potsdam.de
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: kdevelop-devel at kdevelop.org
List-Help: <mailto:kdevelop-devel-request at barney.cs.uni-potsdam.de?subject=help>
List-Post: <mailto:kdevelop-devel at barney.cs.uni-potsdam.de>
List-Subscribe: <http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel>,
	<mailto:kdevelop-devel-request at barney.cs.uni-potsdam.de?subject=subscribe>
List-Id: KDevelop Developer Mailinglist <kdevelop-devel.barney.cs.uni-potsdam.de>
List-Unsubscribe: <http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel>,
	<mailto:kdevelop-devel-request at barney.cs.uni-potsdam.de?subject=unsubscribe>
List-Archive: <http://barney.cs.uni-potsdam.de/mailman/private/kdevelop-devel/>
Date: Mon Dec 12 22:00:13 2005
X-Original-Date: Mon, 12 Dec 2005 14:45:29 -0600

On Mon, Dec 12, 2005 at 08:09:25PM +0200, Alexander Dymo wrote:
> On Monday 12 December 2005 03:51, Matt Rogers wrote:
> > do not revive our copy of bdb. This is system specific to slackware users.
> > they need to specify
> > --with-db-includedir=/usr/include/db4
> > or adjust their /usr/include/db.h symlinks to point to the db 4 version of
> > the header.
> Do we have the guarantee that all versions of bdb work with our code
> completion engine? I know it used to crash under certain conditions.
> Have that been fixed?
> 

Yes, that was a condition that I gave Dirk when he started reenabling
the use of an external copy of bdb.