From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Langhoff Subject: Re: [ANNOUNCE] qgit-0.9 Date: Sun, 14 Aug 2005 21:04:19 +1200 Message-ID: <46a038f905081402049d317e5@mail.gmail.com> References: <20050813121216.15512.qmail@web26305.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: git@vger.kernel.org X-From: git-owner@vger.kernel.org Sun Aug 14 11:05:22 2005 Return-path: Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E4EQO-0006ve-FE for gcvg-git@gmane.org; Sun, 14 Aug 2005 11:05:00 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932375AbVHNJEZ (ORCPT ); Sun, 14 Aug 2005 05:04:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932374AbVHNJEY (ORCPT ); Sun, 14 Aug 2005 05:04:24 -0400 Received: from rproxy.gmail.com ([64.233.170.193]:3634 "EHLO rproxy.gmail.com") by vger.kernel.org with ESMTP id S932375AbVHNJEY convert rfc822-to-8bit (ORCPT ); Sun, 14 Aug 2005 05:04:24 -0400 Received: by rproxy.gmail.com with SMTP id i8so650326rne for ; Sun, 14 Aug 2005 02:04:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SvQX8JUINxbOaqB5i7ekhjhX3bMGgK6i0BB52KnMtzWEx3uUsRzekpVUcfWv/9W1tajc31h54dhuZpxdXafYrY22YR5/Rh8u4azgMuvEOKMdsamMYQC36LHKY2TXpIKGCxDeXWvyR2l8/r4crfmaI1Wm677n1FNW2I9BAbPK6sk= Received: by 10.38.89.29 with SMTP id m29mr1618928rnb; Sun, 14 Aug 2005 02:04:19 -0700 (PDT) Received: by 10.38.101.8 with HTTP; Sun, 14 Aug 2005 02:04:19 -0700 (PDT) To: Marco Costalba In-Reply-To: <20050813121216.15512.qmail@web26305.mail.ukl.yahoo.com> Content-Disposition: inline Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Marco, How do I get this to build on Debian? Not familiar with scons, and it is complaining that it can't find qt and related header files, when they are there... It's been mentioned on the list that v0.3 didn't build on Debian, but I thought it had been dealt with. There were no fixes mentioned on the thread. cheers, martin