From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] ELFUTILS - only build for the target architecture...
Date: Tue, 13 Oct 2020 13:47:12 +0200 [thread overview]
Message-ID: <20201013134712.023269ac@windsurf> (raw)
In-Reply-To: <CACxOKoKEi0OnY+aq1i6S=zX5XnDnu_pMVWtGmEpnDB7CrdW2cw@mail.gmail.com>
Hello Maurice,
On Mon, 12 Oct 2020 17:06:26 -0600
Maurice Smulders via buildroot <buildroot@busybox.net> wrote:
> Currently, ELFUTILS gets built for all architectures it looks like.
>
> safe:/usr/lib/elfutils> ls
> libebl_aarch64-0.177.so libebl_i386.so libebl_s390-0.177.so
> libebl_aarch64.so libebl_ia64-0.177.so libebl_s390.so
> libebl_alpha-0.177.so libebl_ia64.so libebl_sh-0.177.so
> libebl_alpha.so libebl_m68k-0.177.so libebl_sh.so
> libebl_arm-0.177.so libebl_m68k.so libebl_sparc-0.177.so
> libebl_arm.so libebl_ppc-0.177.so libebl_sparc.so
> libebl_bpf-0.177.so libebl_ppc.so libebl_tilegx-0.177.so
> libebl_bpf.so libebl_ppc64-0.177.so libebl_tilegx.so
> libebl_csky-0.177.so libebl_ppc64.so libebl_x86_64-0.177.so
> libebl_csky.so libebl_riscv-0.177.so libebl_x86_64.so
> libebl_i386-0.177.so libebl_riscv.so
I don't see these shared libraries when building elfutils with the
current Buildroot. Could you give more details about your Buildroot
version and configuration ?
> Is there a way to get it built just for the target architecture - in
> our case PowerPC (ppc)? I have added minicoredumper to the
> customization packages, and it requires elfutils....
I think these files are all probably built for your target
architecture, but have support for inspecting ELF files from other CPU
architectures? For example, even if you're on PPC system, you may want
to inspect x86 or ARM binaries. But I'm really just guessing here since
I don't have those shared libraries installed when I build elfutils.
And I see in the libebl/Makefile.am that it's a noinst library, so
libebl should not even be installed. That being said, I admit I'm
building with the latest Buildroot, which has elfutils 0.181 and you're
using elfutils 0.177.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-10-13 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 23:06 [Buildroot] ELFUTILS - only build for the target architecture Maurice Smulders
2020-10-13 11:47 ` Thomas Petazzoni [this message]
2020-10-13 15:25 ` Maurice Smulders
2020-10-13 15:56 ` Thomas Petazzoni
2020-10-13 16:11 ` Maurice Smulders
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=20201013134712.023269ac@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox