On Tue, Feb 07, 2023 at 04:45:47PM +0100, Daniel Wagner wrote: > On Tue, Feb 07, 2023 at 10:10:01AM -0500, Steven Rostedt wrote: > > On Tue, 7 Feb 2023 14:48:25 +0100 > > Daniel Wagner <dwagner@xxxxxxx> wrote: > > > > > On Tue, Feb 07, 2023 at 01:46:32PM +0100, Daniel Wagner wrote: > > > > This version brings a few cleanups on the documentation intallation path > > > > and pkg-config depenedency updates. > > > > > > > > Changes: > > > > > > > > v6: > > > > - lib: isntall trace-cmd.h directly in /usr/include and not subdir > > > > trace-cmd. kernelshark builds breaks otherwise > > > > > > No, this is not the real problem. The Makefile also installs it under > > > /usr/include/trace-cmd. > > > > But `pkg-config --cflags libtracecmd` should give the right path: > > > > -I/usr/include/trace-cmd -I/usr/include/tracefs -I/usr/include/traceevent > > > > This is the way it's always been. Why are your kernelshark builds breaking? > > Not sure what's happening. I've build and installed the library with make > and the kernelshark configuration step still fails. I see the following > output (make and meson): > > $ cmake -S . -B foo --debug-find > Running with debug output on for the `find` commands. There is something wierd going with the libtracecmd build in our build system. It produces a libtrace-cmd.pc and not a libtracecmd.pc file but this was with the v2 version of the meson patches. Doesn't happen with libtracecmd v5. In short, just ignore v6.
|