From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30587 invoked by alias); 7 Jan 2009 12:51:32 -0000 Received: (qmail 30555 invoked by uid 48); 7 Jan 2009 12:51:22 -0000 Date: Wed, 07 Jan 2009 12:51:00 -0000 Message-ID: <20090107125122.30554.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20090107103538.9716.kamalesh@linux.vnet.ibm.com> References: <20090107103538.9716.kamalesh@linux.vnet.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug releng/9716] latest systemtap ./configure build fails with pkgconfig-0.21 X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q1/txt/msg00049.txt.bz2 ------- Additional Comments From fche at redhat dot com 2009-01-07 12:51 ------- (In reply to comment #1) > Possibly SystemTap should not make building docs, remote server, etc., part of > the default 'configure' run, rather have users use --enable- switches > if they need it. > > Basic 'configure' run should be made to run with minimal dependencies and build > just enough binaries to get users started with SystemTap. I think that would be swinging the pendulum too much back. We would not want to require users to rebuild their copy of systemtap if they became aware of things they were missing like ... documentation. What we certainly need is a more careful autoconfing so that everything that is buildable will build, and nothing else is attempted. -- http://sourceware.org/bugzilla/show_bug.cgi?id=9716 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.