All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@uclibc.org
Subject: [Buildroot] Large number of duplicate files in sdk
Date: Wed, 20 Nov 2024 20:00:06 -0000 (UTC)	[thread overview]
Message-ID: <vhlf46$9b9$1@ciao.gmane.io> (raw)

When I do a "make sdk" (using 2024.02.6), the resulting tarball
contains tons of duplicate files.  I'm using an external Linaro ARM
toolchain.  With a fairly bare-bones package selection, the sdk tarball
generated by buildroot appears to be about 40% duplicate files by
size (about 20% by count).  According to a Python app I hacked
together it looks like there are 2300+ duplicated files taking up
380MB of wasted disk space.

[The fdupes utility finds about 100 fewer duplicates than my Python
application, so my numbers might be slightly off.]

Pretty much all of the include and library files from the external
toolchain are found under both ./opt/ext-toolchain/arm-linux-gnueabihf
and again under ./arm-buildroot-linux-gnueabihf/sysroot

Are both copies of all those files needed?

Is there some option to prune unneeded files?

My first impulse was to just delete ./opt/ext-toolchain, but I noticed
that there are couple dozen files under ./bin that are symlinked to
.../opt/ instead of being duplicated like everything else.

--
Grant

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-11-20 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 20:00 Grant Edwards [this message]
2024-11-20 23:27 ` [Buildroot] Large number of duplicate files in sdk Grant Edwards
2024-11-21  8:18   ` Peter Korsgaard
2024-11-21 15:06     ` Grant Edwards

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='vhlf46$9b9$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --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 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.