From: "Michal Suchánek" <msuchanek@suse.de>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andrii Nakryiko <andrii@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
dwarves@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com,
Michael Petlan <mpetlan@redhat.com>
Subject: Re: [RFT] Testing 1.22
Date: Thu, 15 Jul 2021 23:31:20 +0200 [thread overview]
Message-ID: <20210715213120.GJ24916@kitsune.suse.cz> (raw)
In-Reply-To: <YK+41f972j25Z1QQ@kernel.org>
Hello,
when building with system libbpf I get:
[ 40s] make[1]: Nothing to be done for 'preinstall'.
[ 40s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/dwarves-1.21+git175.1ef87b2/build'
[ 40s] Install the project...
[ 40s] /usr/bin/cmake -P cmake_install.cmake
[ 40s] -- Install configuration: "RelWithDebInfo"
[ 40s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/dwarves-1.21+git175.1ef87b2-15.1.ppc64le/usr/bin/codiff
[ 40s] CMake Error at cmake_install.cmake:63 (file):
[ 40s] file RPATH_CHANGE could not write new RPATH:
[ 40s]
[ 40s]
[ 40s]
[ 40s] to the file:
[ 40s]
[ 40s] /home/abuild/rpmbuild/BUILDROOT/dwarves-1.21+git175.1ef87b2-15.1.ppc64le/usr/bin/codiff
[ 40s]
[ 40s] The current RUNPATH is:
[ 40s]
[ 40s] /home/abuild/rpmbuild/BUILD/dwarves-1.21+git175.1ef87b2/build:
[ 40s]
[ 40s] which does not contain:
[ 40s]
[ 40s] /usr/local/lib64:/home/abuild/rpmbuild/BUILD/dwarves-1.21+git175.1ef87b2/build:
[ 40s]
[ 40s] as was expected.
[ 40s]
[ 40s]
[ 40s] make: *** [Makefile:74: install] Error 1
[ 40s] make: Leaving directory '/home/abuild/rpmbuild/BUILD/dwarves-1.21+git175.1ef87b2/build'
[ 40s] error: Bad exit status from /var/tmp/rpm-tmp.OaGNX4 (%install)
This is not a problem with embedded libbpf.
Using system libbpf seems to be new in 1.22
Thanks
Michal
On Thu, May 27, 2021 at 12:20:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Hi guys,
>
> Its important to have 1.22 out of the door ASAP, so please clone
> what is in tmp.master and report your results.
>
> To make it super easy:
>
> [acme@quaco pahole]$ cd /tmp
> [acme@quaco tmp]$ git clone git://git.kernel.org/pub/scm/devel/pahole/pahole.git
> Cloning into 'pahole'...
> remote: Enumerating objects: 6510, done.
> remote: Total 6510 (delta 0), reused 0 (delta 0), pack-reused 6510
> Receiving objects: 100% (6510/6510), 1.63 MiB | 296.00 KiB/s, done.
> Resolving deltas: 100% (4550/4550), done.
> [acme@quaco tmp]$ cd pahole/
> [acme@quaco pahole]$ git checkout origin/tmp.master
> Note: switching to 'origin/tmp.master'.
>
> You are in 'detached HEAD' state. You can look around, make experimental
> changes and commit them, and you can discard any commits you make in this
> state without impacting any branches by switching back to a branch.
>
> If you want to create a new branch to retain commits you create, you may
> do so (now or later) by using -c with the switch command. Example:
>
> git switch -c <new-branch-name>
>
> Or undo this operation with:
>
> git switch -
>
> Turn off this advice by setting config variable advice.detachedHead to false
>
> HEAD is now at 0d17503db0580a66 btf_encoder: fix and complete filtering out zero-sized per-CPU variables
> [acme@quaco pahole]$ git log --oneline -5
> 0d17503db0580a66 (HEAD, origin/tmp.master) btf_encoder: fix and complete filtering out zero-sized per-CPU variables
> fb418f9d8384d3a9 dwarves: Make handling of NULL by destructos consistent
> f049fe9ebf7aa9c2 dutil: Make handling of NULL by destructos consistent
> 1512ab8ab6fe76a9 pahole: Make handling of NULL by destructos consistent
> 1105b7dad2d0978b elf_symtab: Use zfree() where applicable
> [acme@quaco pahole]$ mkdir build
> [acme@quaco pahole]$ cd build
> [acme@quaco build]$ cmake ..
> <SNIP>
> -- Build files have been written to: /tmp/pahole/build
> [acme@quaco build]$ cd ..
> [acme@quaco pahole]$ make -j8 -C build
> make: Entering directory '/tmp/pahole/build'
> <SNIP>
> [100%] Built target pahole
> make[1]: Leaving directory '/tmp/pahole/build'
> make: Leaving directory '/tmp/pahole/build'
> [acme@quaco pahole]$
>
> Then make sure build/pahole is in your path and try your workloads.
>
> Jiri, Michael, if you could run your tests with this, that would be awesome,
>
> Thanks in advance!
>
> - Arnaldo
next prev parent reply other threads:[~2021-07-15 21:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 15:20 [RFT] Testing 1.22 Arnaldo Carvalho de Melo
2021-05-27 16:54 ` Andrii Nakryiko
2021-05-27 19:04 ` Arnaldo
2021-05-27 19:14 ` Andrii Nakryiko
2021-05-27 19:55 ` Arnaldo
2021-05-27 20:41 ` Andrii Nakryiko
2021-05-27 21:08 ` Jiri Olsa
2021-05-27 21:57 ` Arnaldo
2021-05-28 19:45 ` Arnaldo Carvalho de Melo
2021-05-29 2:36 ` Andrii Nakryiko
2021-06-01 18:31 ` Arnaldo Carvalho de Melo
2021-06-01 18:32 ` Arnaldo Carvalho de Melo
2021-05-30 0:40 ` Andrii Nakryiko
2021-06-01 18:24 ` Arnaldo Carvalho de Melo
2021-06-03 14:57 ` Arnaldo Carvalho de Melo
2021-06-05 2:55 ` Andrii Nakryiko
2021-06-07 13:20 ` Parallelizing vmlinux BTF encoding. was " Arnaldo Carvalho de Melo
2021-06-07 15:42 ` Yonghong Song
2021-06-08 0:53 ` Andrii Nakryiko
2021-06-08 12:59 ` Arnaldo Carvalho de Melo
2021-06-15 19:01 ` Arnaldo Carvalho de Melo
2021-06-15 19:13 ` Andrii Nakryiko
2021-06-15 19:38 ` Arnaldo Carvalho de Melo
2021-06-15 20:05 ` Andrii Nakryiko
2021-06-15 20:25 ` Arnaldo Carvalho de Melo
2021-06-15 21:26 ` Andrii Nakryiko
2021-05-30 21:45 ` Jiri Olsa
2021-06-01 19:07 ` Arnaldo Carvalho de Melo
2021-06-02 10:21 ` Michael Petlan
2021-07-15 21:31 ` Michal Suchánek [this message]
2021-07-16 13:25 ` Arnaldo Carvalho de Melo
2021-07-16 13:35 ` Luca Boccassi
2021-07-16 19:08 ` Luca Boccassi
[not found] ` <20210716201248.GL24916@kitsune.suse.cz>
2021-07-17 14:35 ` Luca Boccassi
2021-07-17 15:10 ` Michal Suchánek
2021-07-17 15:14 ` Luca Boccassi
2021-07-17 16:36 ` Michal Suchánek
2021-07-17 16:39 ` Luca Boccassi
2021-07-19 10:30 ` Michal Suchánek
2021-07-19 10:34 ` Luca Boccassi
2021-07-19 12:10 ` Luca Boccassi
2021-07-19 21:08 ` Arnaldo Carvalho de Melo
2021-07-28 10:53 ` Expected release date of v1.22 Deepak Kumar Mishra
2021-07-28 11:21 ` Greg KH
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=20210715213120.GJ24916@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=mpetlan@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).