From: Qais Yousef <qais.yousef@arm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 4/4] clang: Fix undefined reference to dladdr error
Date: Sat, 3 Oct 2020 21:58:01 +0100 [thread overview]
Message-ID: <20201003205801.dgxdehckx2uun3yk@e107158-lin.cambridge.arm.com> (raw)
In-Reply-To: <9384100b-8c1d-9982-cd27-b2f6ed03dddf@gmail.com>
On 09/29/20 22:59, Romain Naour wrote:
> Hi Qais,
>
> Le 29/09/2020 ? 12:26, Qais Yousef a ?crit?:
> > For some reason the cmake::find_library() can't detect the path to dl,
> > so we end up not including the right library when linking, hence the
> > error above.
> >
> > Could be a hack/workaround to the real problem.
>
> I'm not sure about this patch. Can you describe how to reproduce the issue?
It just complained about not finding the library. Hit the same issue when
building Jugurtha BCC patch. Maybe something wrong in my environment.
Will try to reproduce and copy the full error message.
Thanks!
--
Qais Yousef
next prev parent reply other threads:[~2020-10-03 20:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 10:26 [Buildroot] [RFC PATCH 0/4] add BCC and bpftrace packages Qais Yousef
2020-09-29 10:26 ` [Buildroot] [RFC PATCH 1/4] llvm: Add BPF backend Qais Yousef
2020-09-29 19:35 ` Romain Naour
2020-09-30 14:38 ` Qais Yousef
2020-09-29 10:26 ` [Buildroot] [RFC PATCH 2/4] Add BPF Compiler Collection (BCC) Package Qais Yousef
2020-09-29 20:33 ` Romain Naour
2020-10-03 20:39 ` Qais Yousef
2020-09-29 10:26 ` [Buildroot] [RFC PATCH 3/4] Add bpftrace package Qais Yousef
2020-09-29 20:55 ` Romain Naour
2020-10-03 20:56 ` Qais Yousef
2020-10-04 20:10 ` Qais Yousef
2020-10-08 22:31 ` Qais Yousef
2020-09-29 10:26 ` [Buildroot] [RFC PATCH 4/4] clang: Fix undefined reference to dladdr error Qais Yousef
2020-09-29 20:59 ` Romain Naour
2020-10-03 20:58 ` Qais Yousef [this message]
2020-10-04 16:12 ` Qais Yousef
2020-09-29 21:08 ` [Buildroot] [RFC PATCH 0/4] add BCC and bpftrace packages Romain Naour
2020-10-01 20:46 ` Qais Yousef
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=20201003205801.dgxdehckx2uun3yk@e107158-lin.cambridge.arm.com \
--to=qais.yousef@arm.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.