From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/sentry-cli: new package
Date: Sat, 19 Sep 2020 22:50:09 +0200 [thread overview]
Message-ID: <20200919225009.321abe29@windsurf> (raw)
In-Reply-To: <20200915205738.2144347-1-joseph.kogut@gmail.com>
Hello,
On Tue, 15 Sep 2020 13:57:38 -0700
Joseph Kogut <joseph.kogut@gmail.com> wrote:
> Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com>
I did some more testing, and after building zlib for the host, the
build fails with:
*** ERROR: package host-libzlib installs executables without proper RPATH:
*** /home/thomas/projets/buildroot/output/host/bin/sentry-cli
Indeed, sentry-cli is linked with libz.so.1:
0x0000000000000001 (NEEDED) Shared library: [libz.so.1]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
0x0000000000000001 (NEEDED) Shared library: [ld-linux-x86-64.so.2]
0x0000000000000001 (NEEDED) Shared library: [libdl.so.2]
0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0]
0x0000000000000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x0000000000000001 (NEEDED) Shared library: [libm.so.6]
I've seen that sentry-cli bundles OpenSSL (it seems), which is perhaps
why it links against libz.so.1.
However, this means that sentry-cli should depend on host-zlib and
should have a RPATH to $(HOST_DIR)/lib.
Could you have a look into this ? I've added in Cc some folks working
on Cargo integration in Buildroot, to see if they can help.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-19 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 20:57 [Buildroot] [PATCH] package/sentry-cli: new package Joseph Kogut
2020-09-15 22:24 ` Titouan Christophe
2020-09-19 20:46 ` Thomas Petazzoni
2020-09-19 20:50 ` Thomas Petazzoni [this message]
2020-09-19 21:08 ` Joseph Kogut
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=20200919225009.321abe29@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.