From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Jonathan Borne <jborne@kalray.eu>
Cc: jmaselbas@kalray.eu, buildroot@buildroot.org, ysionneaux@kalray.eu
Subject: Re: [Buildroot] [RFC PATCH 0/1] Fix binutils/libiberty target install directory
Date: Mon, 24 Jan 2022 19:44:29 +0200 [thread overview]
Message-ID: <87k0ep9gbx.fsf@tarshish> (raw)
In-Reply-To: <20220124173521.2236-1-jborne@kalray.eu>
Hi Jonathan,
On Mon, Jan 24 2022, Jonathan Borne via buildroot wrote:
> Hi,
> I stumbled upon a suspicious line in binutils.mk.
>
> In BINUTILS_INSTALL_TARGET_CMDS,
> libopcode and libbfd DESTDIR are both set to $(TARGET_DIR)
> and libiberty is the only one set to $(STAGING_DIR).
>
> Is there a reason behind this?
As I understand that's because libiberty is static only. Buildroot does
not copy static libraries to $(TARGET_DIR) because they are only used at
build time, but not at run-time.
baruch
> Sorry if this is an obvious question, I am quite new to buildroot.
> I assume I am probably missing something.
> I though it was still better to ask...
>
> Thanks
> Best regards.
> Jonathan.
>
>
> Jonathan Borne(1):
> Fix binutils/libiberty target install directory.
>
> package/binutils/binutils.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-24 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 17:35 [Buildroot] [RFC PATCH 0/1] Fix binutils/libiberty target install directory Jonathan Borne via buildroot
2022-01-24 17:35 ` [Buildroot] [RFC PATCH 1/1] " Jonathan Borne via buildroot
2022-01-24 17:44 ` Baruch Siach via buildroot [this message]
2022-01-24 18:12 ` [Buildroot] [RFC PATCH 0/1] " Romain Naour
2022-01-24 21:02 ` Thomas Petazzoni
2022-01-24 21:21 ` Yann E. MORIN
2022-01-24 21:53 ` Thomas Petazzoni
2022-01-26 15:30 ` Jonathan Borne via buildroot
2022-01-26 15:52 ` Thomas Petazzoni
2022-01-26 17:14 ` Yann E. MORIN
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=87k0ep9gbx.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=jborne@kalray.eu \
--cc=jmaselbas@kalray.eu \
--cc=ysionneaux@kalray.eu \
/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