On 19 October 2014 17:45, Christian Hofstaedtler wrote:
> No, I don't know where systemtap would look for the file. If that
> locations works, that's fine with me.
Apparently systemtap expects tapfiles to be located in "x86_64" on amd64
systems and in "i386" on i386 systems. However, DEB_HOST_GNU
Hi,
* Sebastian Boehm [141019 17:06]:
> On 19 October 2014 15:17, Christian Hofstaedtler wrote:
>
> > I think this would break Multi-Arch co-installability of libruby2.1
> > (a file that differs between architectures gets installed in the
> > same location on different architectures).
> >
> > I
Hi,
On 19 October 2014 15:17, Christian Hofstaedtler wrote:
> I think this would break Multi-Arch co-installability of libruby2.1
> (a file that differs between architectures gets installed in the
> same location on different architectures).
>
> If you could sort this out I'd likely apply your p
* Sebastian Boehm [141018 20:57]:
> Package: libruby2.1
> Version: 2.1.3-1
>
> While Ruby supports SystemTap, a dynamic tracing framework for Linux
> (see #747232), at the moment the Debian package does not ship with a
> tapfile to facilitate tracing Ruby programs.
>
> The attached patch adds th
Package: libruby2.1
Version: 2.1.3-1
While Ruby supports SystemTap, a dynamic tracing framework for Linux
(see #747232), at the moment the Debian package does not ship with a
tapfile to facilitate tracing Ruby programs.
The attached patch adds the tapfile used in Fedora and modifies the
packaging
5 matches
Mail list logo
