This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: cyclic build dependency libvirt->systemtap->libvirt?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Timo Juhani Lindfors <timo dot lindfors at iki dot fi>
- Cc: systemtap at sourceware dot org
- Date: Mon, 07 Apr 2014 10:20:57 -0400
- Subject: Re: cyclic build dependency libvirt->systemtap->libvirt?
- Authentication-results: sourceware.org; auth=none
- References: <84vbulqqi2 dot fsf at sauna dot l dot org>
timo.lindfors wrote:
> systemtap 2.4 seems to use libvirt headers during build. In debian
> libvirt also uses systemtap sdt.h during build. Is this intentional or
> should we try to mitigate this somehow?
Good catch. It's a loosely-versioned dependency (any previous version
of X is enough to build Y), so updates are not really problematic. If
it's really worth solving, I suppose one could fork the sdt-devel
header file into its own separate package (versus being a
sub-package).
> Cyclic build dependencies are problematic e.g. when porting software
> to new architectures or compilers (such as clang).
For bootstrapping purposes, the loop may be broken at either point by
removing the rpm/dep dependency tags, and building either package in
isolation.
- FChE