From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] Can we build static host tools (e.g. tar)?
Date: Thu, 23 Jan 2025 17:40:41 -0000 (UTC) [thread overview]
Message-ID: <vmtuup$11q0$1@ciao.gmane.io> (raw)
In-Reply-To: 929cc71a-1d78-46b7-b99f-99936c9fff20@mind.be
On 2025-01-23, Arnout Vandecappelle via buildroot <buildroot@buildroot.org> wrote:
> On 14/01/2025 17:24, Grant Edwards wrote:
>> I'm having problems with the SDK that Buildroot builds. Things like
>> opkg-build are failing because they're using buildroot's SDK version
>> of tar, and the glibc version isn't compatible between the host where
>> the sdk was built and the devleoper host where the sdk is being used.
>
> The SDK is meant to be relocatable, but it is very hard to make it possible to
> just run anywhere. Static linking can help but even with -static you may still
> get a shared binary. So even if we do that, there's no guarantee that it will
> work on another build machine.
Right, but it should reduce the areas that could cause problems
(though static binaries would probably end up being absurding large).
> BTW I'm surprised you complain about tar - the compiler should have the same
> issue, no?
The change that's tripping us up was at glibc 2.38. So far, the only
change we've run into using the SDK that wasn't compatible was in
libacl, and the only thing that uses that in the SDK (at least for us)
is tar.
Our temporary work-around is to go into the sdk tree on the affected
hosts and replace 'tar' with a symlink to the host's native
tar. Eventually those hosts will get OS updates that will allow the
SDK's tar to work again.
--
Grant
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-01-23 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 16:24 [Buildroot] Can we build static host tools (e.g. tar)? Grant Edwards
2025-01-23 17:22 ` Arnout Vandecappelle via buildroot
2025-01-23 17:40 ` Grant Edwards [this message]
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='vmtuup$11q0$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
--cc=buildroot@uclibc.org \
/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