bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Michal Suchánek" <msuchanek@suse.de>,
	"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: Mon, 19 Jul 2021 13:10:52 +0100	[thread overview]
Message-ID: <d5b963695314f66240b96f5699a78f0d980a0b44.camel@debian.org> (raw)
In-Reply-To: <YPGIxJao9SrsiG9X@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]

On Fri, 2021-07-16 at 10:25 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jul 15, 2021 at 11:31:20PM +0200, Michal Suchánek escreveu:
> > 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
> 
> Lucca, can you take a look at this?
> 
> Thanks,
> 
> - Arnaldo

Arnaldo, just to give you a quick summary and close the loop in case
you haven't followed the (very verbose) thread: the root cause was a
packaging issue of libbpf in SUSE, which is now solved, and the
reported build problem is now gone:

https://build.opensuse.org/package/show/home:michals/dwarves

-- 
Kind regards,
Luca Boccassi

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-07-19 12:10 UTC|newest]

Thread overview: 42+ 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
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 [this message]
2021-07-19 21:08       ` Arnaldo Carvalho de Melo

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=d5b963695314f66240b96f5699a78f0d980a0b44.camel@debian.org \
    --to=bluca@debian.org \
    --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 \
    --cc=msuchanek@suse.de \
    /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).