All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Matt Turner <mattst88@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v8 0/3] perf tools: port UI from GTK2 to GTK4
Date: Wed, 9 Sep 2026 17:02:59 -0300	[thread overview]
Message-ID: <aqG7c7RkOoaxMo1w@x2> (raw)
In-Reply-To: <aqFIkFzVvCQqnzpy@x2>

On Wed, Sep 09, 2026 at 08:52:48AM -0300, Arnaldo Carvalho de Melo wrote:
> On Wed, Sep 09, 2026 at 08:43:20AM -0300, Arnaldo Carvalho de Melo wrote:
> > On Wed, Sep 09, 2026 at 08:35:20AM -0300, Arnaldo Carvalho de Melo wrote:
> > Now, with GTK4=1 and trying to build the first patch after installing
> > gtk4-devel on fedora 43 it fails to detect gtk4 support:
> > 
> > ⬢ [acme@toolbx perf-tools-next]$ m
> > make: Entering directory '/home/acme/git/perf-tools-next/tools/perf'
> >   BUILD:   Doing 'make -j32' parallel build
> > 
> > Auto-detecting system features:
> > ...                                   libdw: [ on  ]
> > ...                                   glibc: [ on  ]
> > ...                                    gtk4: [ OFF ]


I removed gtk4 from FEATURES_DISPLAY, as it is opt-in, no point in
telling most of the time it is OFF, when developing one can use 'make
VF=1' to see if it was detected:

⬢ [acme@toolbx perf-tools-next]$ alias m='rm -rf ~/libexec/perf-core/ ; make VF=1 CORESIGHT=1 -k O=/tmp/build/$(basename $PWD)/ -C tools/perf install-bin && perf test import && cat /tmp/build/$(basename $PWD)/feature/test-all.make.output' ; export PYTHONPATH=/tmp/build/$(basename $PWD)/python
⬢ [acme@toolbx perf-tools-next]$ m
make: Entering directory '/home/acme/git/perf-tools-next/tools/perf'
  BUILD:   Doing 'make -j32' parallel build

Auto-detecting system features:
...                                   libdw: [ on  ]
...                                   glibc: [ on  ]
...                                  libelf: [ on  ]
...                                 libnuma: [ on  ]
...                  numa_num_possible_cpus: [ on  ]
...                               libpython: [ on  ]
...                             libcapstone: [ on  ]
...                               llvm-perf: [ on  ]
...                                    zlib: [ on  ]
...                                    lzma: [ on  ]
...                                     bpf: [ on  ]
...                                  libaio: [ on  ]
...                                 libzstd: [ on  ]
...                              libopenssl: [ on  ]
...                                    rust: [ on  ]
...                               backtrace: [ on  ]
...                                 eventfd: [ on  ]
...                          fortify-source: [ on  ]
...                                  gettid: [ on  ]
...                                  libbfd: [ on  ]
...                       libbfd-threadsafe: [ on  ]
...                       libelf-getphdrnum: [ on  ]
...                     libelf-gelf_getnote: [ on  ]
...                    libelf-getshdrstrndx: [ on  ]
...                             libelf-zstd: [ on  ]
...                                libslang: [ on  ]
...                           libtraceevent: [ on  ]
...                             libcpupower: [ on  ]
...             pthread-attr-setaffinity-np: [ on  ]
...                         pthread-barrier: [ on  ]
...                            reallocarray: [ on  ]
...                      stackprotector-all: [ on  ]
...                                 timerfd: [ on  ]
...                               scandirat: [ on  ]
...                            sched_getcpu: [ on  ]
...                                     sdt: [ on  ]
...                                   setns: [ on  ]
...                  disassembler-four-args: [ on  ]
...                disassembler-init-styled: [ on  ]
...                             file-handle: [ on  ]
...                                  bionic: [ OFF ]
...                              compile-32: [ OFF ]
...                             compile-x32: [ OFF ]
...                          cplus-demangle: [ OFF ]
...                            cxa-demangle: [ on  ]
...                                    gtk4: [ OFF ]
...                                   hello: [ OFF ]
...                  babeltrace2-ctf-writer: [ on  ]
...                             libcapstone: [ on  ]
...                                libcheck: [ OFF ]
...                          libbfd-liberty: [ OFF ]
...                        libbfd-liberty-z: [ OFF ]
...                              libopencsd: [ on  ]
...                                 libperl: [ OFF ]
...                                    llvm: [ OFF ]
...                                  libbpf: [ OFF ]
...                                 libpfm4: [ on  ]
...                           libdebuginfod: [ on  ]
...                         clang-bpf-co-re: [ on  ]
...                       bpftool-skeletons: [ OFF ]
...                               libunwind: [ OFF ]
...                   libunwind-debug-frame: [ OFF ]
...                       libunwind-aarch64: [ OFF ]
...           libunwind-debug-frame-aarch64: [ OFF ]
...                           libunwind-arm: [ OFF ]
...               libunwind-debug-frame-arm: [ OFF ]
...                   libunwind-loongarch64: [ OFF ]
...       libunwind-debug-frame-loongarch64: [ OFF ]
...                          libunwind-mips: [ OFF ]
...              libunwind-debug-frame-mips: [ OFF ]
...                         libunwind-ppc32: [ OFF ]
...             libunwind-debug-frame-ppc32: [ OFF ]
...                         libunwind-ppc64: [ OFF ]
...             libunwind-debug-frame-ppc64: [ OFF ]
...                         libunwind-riscv: [ OFF ]
...             libunwind-debug-frame-riscv: [ OFF ]
...                         libunwind-s390x: [ OFF ]
...             libunwind-debug-frame-s390x: [ OFF ]
...                           libunwind-x86: [ OFF ]
...               libunwind-debug-frame-x86: [ OFF ]
...                        libunwind-x86_64: [ OFF ]
...            libunwind-debug-frame-x86_64: [ OFF ]
...                                  prefix: /home/acme
...                                  bindir: /home/acme/bin
...                                  libdir: /home/acme/lib64
...                              sysconfdir: /home/acme/etc
...                           LIBUNWIND_DIR:
...                               LIBDW_DIR:
...                                    JDIR: /usr/lib/jvm/java-latest-openjdk
...               DWARF post unwind library: libdw


- Arnaldo

      reply	other threads:[~2026-09-09 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  2:50 [PATCH v8 0/3] perf tools: port UI from GTK2 to GTK4 Matt Turner
2026-09-09  2:50 ` [PATCH v8 1/3] tools: port perf ui from GTK 2 to GTK 4 Matt Turner
2026-09-09  3:06   ` sashiko-bot
2026-09-09  2:50 ` [PATCH v8 2/3] perf tools: make the GTK4 report browser actually loadable at runtime Matt Turner
2026-09-09  3:01   ` sashiko-bot
2026-09-09  2:50 ` [PATCH v8 3/3] perf tools gtk: fix two hierarchy-view stack buffer overflows Matt Turner
2026-09-09  3:10   ` sashiko-bot
2026-09-09 11:13 ` [PATCH v8 0/3] perf tools: port UI from GTK2 to GTK4 Arnaldo Carvalho de Melo
2026-09-09 11:25   ` Arnaldo Carvalho de Melo
2026-09-09 11:29     ` Arnaldo Carvalho de Melo
2026-09-09 11:35       ` Arnaldo Carvalho de Melo
2026-09-09 11:43         ` Arnaldo Carvalho de Melo
2026-09-09 11:52           ` Arnaldo Carvalho de Melo
2026-09-09 20:02             ` Arnaldo Carvalho de Melo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aqG7c7RkOoaxMo1w@x2 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mattst88@gmail.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.