From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 3/3] package/elf2flt: fix build with binutils >= 2.41 due to libbfd location
Date: Sun, 6 Aug 2023 15:45:47 +0200 [thread overview]
Message-ID: <20230806154547.308be861@windsurf> (raw)
In-Reply-To: <878rao78e2.fsf@tarshish>
On Sun, 06 Aug 2023 13:47:41 +0300
Baruch Siach via buildroot <buildroot@buildroot.org> wrote:
> > +# elf2flt needs to link against libbfd.a and libiberty.a which are
> > +# provided by host-binutils, but not installed, so we poke directory
>
> s/directory/directly/, I believe.
>
> The same issue in also the commit log above.
Good point, fixed when applying! Thanks for the review.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-06 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 10:25 [Buildroot] [PATCH 1/3] package/elf2flt: refresh patches Thomas Petazzoni via buildroot
2023-08-06 10:25 ` [Buildroot] [PATCH 2/3] package/elf2flt: backport upstream patch to remove use of BFD_VMA_FMT Thomas Petazzoni via buildroot
2023-08-06 10:25 ` [Buildroot] [PATCH 3/3] package/elf2flt: fix build with binutils >= 2.41 due to libbfd location Thomas Petazzoni via buildroot
2023-08-06 10:47 ` Baruch Siach via buildroot
2023-08-06 13:45 ` Thomas Petazzoni via buildroot [this message]
2023-08-06 12:54 ` [Buildroot] [PATCH 1/3] package/elf2flt: refresh patches Waldemar Brodkorb
2023-08-06 13:43 ` Thomas Petazzoni via buildroot
2023-08-06 13:45 ` Thomas Petazzoni via buildroot
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=20230806154547.308be861@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@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 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.