All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qais Yousef <qais.yousef@arm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 3/4] Add bpftrace package
Date: Sun, 4 Oct 2020 21:10:13 +0100	[thread overview]
Message-ID: <20201004201013.ne5k455yagewtlxr@e107158-lin.cambridge.arm.com> (raw)
In-Reply-To: <20201003205623.2okstxwxa6fk5eqb@e107158-lin.cambridge.arm.com>

On 10/03/20 21:56, Qais Yousef wrote:

[...]

> > > diff --git a/package/bpftrace/Config.in b/package/bpftrace/Config.in
> > > new file mode 100644
> > > index 0000000000..a4bae478dc
> > > --- /dev/null
> > > +++ b/package/bpftrace/Config.in
> > > @@ -0,0 +1,27 @@
> > > +config BR2_PACKAGE_BPFTRACE
> > > +	bool "bpftrace"
> > > +	depends on BR2_aarch64 || BR2_aarch64_be || BR2_x86_64
> > > +	depends on BR2_PACKAGE_BCC
> > > +	depends on BR2_PACKAGE_LLVM_RTTI
> > 
> > Why llvm rtti is needed ?
> 
> Good question.
> 
> I think I was seeing failures similar to the one described in the link below.
> Something wasn't found in LLVM library without enabling this option. Will try
> to reproduce and document it better. Unless you know of a better way to handle
> these type of problems :-)
> 
> 	https://github.com/iovisor/bpftrace/issues/1156

This is the error that I get if I don't enable LLVM_RTTI:

buildroot-arm64/output/host/lib/gcc/aarch64-buildroot-linux-gnu/9.3.0/../../../../aarch64-buildroot-linux-gnu/bin/ld: ast/libast.so: undefined reference to `typeinfo for llvm::SectionMemoryManager'
buildroot-arm64/output/host/lib/gcc/aarch64-buildroot-linux-gnu/9.3.0/../../../../aarch64-buildroot-linux-gnu/bin/ld: ast/libast.so: undefined reference to `typeinfo for llvm::orc::SymbolResolver'
collect2: error: ld returned 1 exit status

I understood after a bit of digging that it has hard dependency on having RTTI
enabled.

Is there a preferred way to solve these type of problems?

Thanks

--
Qais Yousef

  reply	other threads:[~2020-10-04 20:10 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 [this message]
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
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=20201004201013.ne5k455yagewtlxr@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.