[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] linux-perf in chroot via .deb abuse
From: |
Vadim Zeitlin |
Subject: |
Re: [lmi] linux-perf in chroot via .deb abuse |
Date: |
Sat, 3 Oct 2020 18:57:27 +0200 |
On Sat, 3 Oct 2020 16:49:44 +0000 Greg Chicares <gchicares@sbcglobal.net> wrote:
GC> On 2020-10-03 11:39, Greg Chicares wrote:
GC> > On 2020-10-03 11:21, Vadim Zeitlin wrote:
GC> >> On Fri, 2 Oct 2020 23:06:27 +0000 Greg Chicares
<gchicares@sbcglobal.net> wrote:
GC> >
GC> > [...cp perf and each library it needs into a chroot...]
GC> >
GC> >> GC> Vadim--Do you think this approach is worse than trying to compile
GC> >> GC> 'perf' in a chroot with the host's kernel version? It just seemed
GC> >> GC> easier to try this way first.
GC>
GC> [...hardlink perf and each library it needs to a directory that will be
mounted in chroots...]
GC>
GC> This way seems smarter:
GC>
GC> http://www.brendangregg.com/perf.html#Building
GC>
GC> | 10.1. Static Builds
GC> |
GC> | I've sometimes done this so that I have a single perf binary that can be
GC> | copied into Docker containers for execution. Steps, given the Linux
source:
GC> |
GC> | cd tools/perf
GC> | vi Makefile.perf
GC> | LDFLAGS=-static
GC> | make clean; make
Ah, yes, this seems like by far the simplest solution, thanks for finding
it and letting me know about it!
VZ
pgpEWKRJ93Xj1.pgp
Description: PGP signature