trace-cmd v2.5.2 broke the kernelshark build by adding the trace-hooks.o
object to the wrong set of files.

Because this update does not change any of the functionality of trace-cmd
itself, it is staying at 2.5.2. This tag is only to fix the build of
kernelshark.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAABAgAGBQJU1NAzAAoJEEjnJuOKh9ldlOYH/145Cc7vwJPie3HGrx1BmIl1
S4XwYEqnmIp0bpnen+QEg2Q7CgP8NFyGRPpKvPdt6AhuOncoHNBLc7mkiyrCroOO
/C4cyhRA9GAu/vAP6fK3PwR/FEbmX9uam7au9ZqSgbrrjyVa8GJLsb1jiNiJKCJD
Cp2g3HMEFkpXwLYKntj8z8BbHC2qO3ykk/3mXqyQyi08FCd4TFi3m5jQ5oZFTKEZ
CVBRI2mWQjixWufrduQcHE/IyqH3K2TehiLGYd4w0/Hxl3p+pPZwnHxje06mMtI6
6a7/1gE4SGrv2M4FzJL0u7nuLOqySVik/QQGodzAziZ+PzARcf7xXPF7dqnhvOk=
=6hJG
-----END PGP SIGNATURE-----
trace-cmd build: Add trace-hooks.o to library files

kernelshark links against libtracecmd.a. The hook functions are now
part of that, but trace-hooks.o was only linked to the trace-cmd object
itself and not the library. This broke the build of kernelshark.

Reported-by: Christian Neukirchen <chneukirchen@gmail.com>
Reported-by: Troy Engel <troyengel@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
1 file changed