cyclic build dependency libvirt->systemtap->libvirt?
Frank Ch. Eigler
fche@redhat.com
Mon Apr 7 14:21:00 GMT 2014
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
More information about the Systemtap
mailing list