From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug releng/9716] latest systemtap ./configure build fails with pkgconfig-0.21
Date: Wed, 07 Jan 2009 12:51:00 -0000 [thread overview]
Message-ID: <20090107125122.30554.qmail@sourceware.org> (raw)
In-Reply-To: <20090107103538.9716.kamalesh@linux.vnet.ibm.com>
------- 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-<doc/...> 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.
next prev parent reply other threads:[~2009-01-07 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 10:35 [Bug releng/9716] New: " kamalesh at linux dot vnet dot ibm dot com
2009-01-07 10:44 ` [Bug releng/9716] " ananth at in dot ibm dot com
2009-01-07 10:53 ` srikar at linux dot vnet dot ibm dot com
2009-01-07 10:55 ` kamalesh at linux dot vnet dot ibm dot com
2009-01-07 11:12 ` srikar at linux dot vnet dot ibm dot com
2009-01-07 12:51 ` fche at redhat dot com [this message]
2009-01-07 19:19 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090107125122.30554.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).