This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: cyclic build dependency libvirt->systemtap->libvirt?
- From: Josh Stone <jistone at redhat dot com>
- To: systemtap at sourceware dot org
- Date: Mon, 07 Apr 2014 09:47:47 -0700
- Subject: Re: cyclic build dependency libvirt->systemtap->libvirt?
- Authentication-results: sourceware.org; auth=none
- References: <84vbulqqi2 dot fsf at sauna dot l dot org> <y0m1tx98bli dot fsf at fche dot csb>
On 04/07/2014 07:20 AM, Frank Ch. Eigler wrote:
>
> 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).
I've had an idea to make a libsdt.so reader, and it would be quite
natural IMO for sdt-devel stuff to live in the same standalone project.
Thoughts?