From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: <yann.morin@orange.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/scripts/check-host-libs: add new check on host binaries/libs
Date: Tue, 20 Sep 2022 11:54:59 +0200 [thread overview]
Message-ID: <20220920115459.2aca37f7@windsurf> (raw)
In-Reply-To: <29653_1663666853_63298AA5_29653_380_1_20220920094051.GE3551@tl-lnx-nyma7486>
On Tue, 20 Sep 2022 11:40:51 +0200
<yann.morin@orange.com> wrote:
> That's because in your script, 'file' reads in DB for every file, while
> the above only loads the DB for each set of a lot of files at once.
Ah, yes, indeed.
Another possibility is to not use "file" and just look at the first 4
bytes of the files to identify ELF files, because that's really what
matters.
> What is the policy on requiring a pyhon interpreter on the host for
> mandatory Buildroot infra? In my experience, doing things in python
> rather than in shell, does indeed speed up things quite substantially.
We have indeed dropped python on the host as a requirement for the
build some time ago. Probably doesn't make sense to reintroduce this
requirement "just" for this. Even though practically speaking, a lot of
the tooling around Buildroot (pkg-stats, graphs, etc.) already relies
on Python, and most people are very likely to have Python installed
anyway.
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:[~2022-09-20 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 6:45 [Buildroot] [PATCH] support/scripts/check-host-libs: add new check on host binaries/libs Thomas Petazzoni
2022-09-20 7:46 ` yann.morin
2022-09-20 8:35 ` Thomas Petazzoni
2022-09-20 9:11 ` yann.morin
2022-09-20 9:19 ` Thomas Petazzoni via buildroot
2022-09-20 9:40 ` yann.morin
2022-09-20 9:54 ` Thomas Petazzoni [this message]
2022-09-20 19:48 ` Arnout Vandecappelle
2022-09-21 7:26 ` yann.morin
2022-09-21 8:23 ` David Laight
2022-09-21 8:41 ` yann.morin
2022-09-21 9:05 ` Thomas Petazzoni via buildroot
2022-09-21 9:09 ` yann.morin
2022-09-21 9:24 ` David Laight
2023-04-16 20:10 ` 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=20220920115459.2aca37f7@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin@orange.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