From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/oprofile: fix static build with binutils >= 2.40
Date: Mon, 6 May 2024 21:45:51 +0200 [thread overview]
Message-ID: <20240506214551.4fda91cf@windsurf> (raw)
In-Reply-To: <20240506070049.137839-1-fontaine.fabrice@gmail.com>
On Mon, 6 May 2024 09:00:49 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> sframe library was added by binutils 2.40 and
> https://github.com/bminor/binutils-gdb/commit/19e559f1c91bfaedbd2f91d85ee161f3f03fda3c
> resulting in the following static build failure:
>
> /home/buildroot/autobuild/run/instance-1/output-1/build/binutils-2.41/bfd/elf-sframe.c:220: undefined reference to `sframe_decode'
>
> [...]
>
> configure: error: bfd library not found
>
> Fixes:
> - http://autobuild.buildroot.org/results/a9f3e09e6543b3773440c011e93bd41e357691e4
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...-fix-static-build-with-binutils-2.40.patch | 62 +++++++++++++++++++
> package/oprofile/oprofile.mk | 7 +++
> 2 files changed, 69 insertions(+)
> create mode 100644 package/oprofile/0002-fix-static-build-with-binutils-2.40.patch
Life would *really* be easier if binutils was installing a libbfd.pc,
and oprofile would use it to detect libbfd and automatically know about
its indirect dependencies.
But oh well, patch applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-06 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 7:00 [Buildroot] [PATCH 1/1] package/oprofile: fix static build with binutils >= 2.40 Fabrice Fontaine
2024-05-06 19:45 ` Thomas Petazzoni via buildroot [this message]
2024-05-27 5:59 ` Peter Korsgaard
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=20240506214551.4fda91cf@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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