From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/4] lmbench: emulate --prefix to avoid scattering binaries all over
Date: Mon, 17 May 2021 18:59:05 +0200 [thread overview]
Message-ID: <20210517165905.GB2506@scaer> (raw)
In-Reply-To: <e39b28e8-79c9-df44-5113-82af630ebdfb@synopsys.com>
Vineet, All,
On 2021-05-10 20:22 +0000, Vineet Gupta via buildroot spake thusly:
> On 5/10/21 1:09 PM, Thomas Petazzoni wrote:
> > On Mon, 10 May 2021 11:00:48 -0700
> > Vineet Gupta via buildroot <buildroot@busybox.net> wrote:
> >
> >> - moves all lmbench binaries to <target>/lmbench/bin/<ARCH>
> >> - scripts copied to <target>/lmbench/scripts
> >> - scripts/os overwritten to setup "OS" as expected by LMBench runtime scripts
> >>
> >> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
> > Where are lmbench binaries currently installed? Because /lmbench/ looks
> > really really odd as an installation location.
>
> They are currently scattered over in /usr/sbin I think.
$ cat output/cat build/lmbench-3.0-a9/.files-list.txt
lmbench,./usr/bin/bw_file_rd
lmbench,./usr/bin/bw_mem
lmbench,./usr/bin/bw_mmap_rd
[...]
lmbench,./usr/bin/stream
lmbench,./usr/bin/timing_o
lmbench,./usr/bin/tlb
lmbench,./usr/lib/libmbench.a
That is, everything is in /usr/bin, except for the static library
(which gets trimmed away during tsarget-finalize anyway) which is in
/usr/lib/.
And apart from the tools and the static library, nothing else is
installed, not even a header, so the the static library is only private
to lmbench anyway.
> Indeed /lmbench is non LSB etc, but it is one stop shop if one wanted to
> remove everything lmbench specific from target rootfs.
> I guess one could do /usr/sbin/lmbench/{bin,scripts}
But why would you want to enable lmbench, and remove it from target?
So, for me, there is no reason for this patch: lmbench already installs
everything in standard locations, and if one does not want lmbench tools
on the target, just do not enable the lmbench package to begin with.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-05-17 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 18:00 [Buildroot] [PATCH v3 0/4] Updates for ARC, LMBench Vineet Gupta
2021-05-10 18:00 ` [Buildroot] [PATCH v3 1/4] ARC: config: explicit'ify -mcpu for cpu selection Vineet Gupta
2021-05-17 19:24 ` Yann E. MORIN
2021-05-10 18:00 ` [Buildroot] [PATCH v2 2/3] lmbench: increase memsize delay for slow FPGAs Vineet Gupta
2021-05-10 18:00 ` [Buildroot] [PATCH v3 2/4] lmbench: memsize: increase " Vineet Gupta
2021-05-17 20:09 ` Yann E. MORIN
2021-05-17 21:53 ` Vineet Gupta
2021-05-18 6:38 ` Yann E. MORIN
2021-05-20 8:41 ` Peter Korsgaard
2021-05-10 18:00 ` [Buildroot] [PATCH v3 3/4] lmbench: emulate --prefix to avoid scattering binaries all over Vineet Gupta
2021-05-10 20:09 ` Thomas Petazzoni
2021-05-10 20:22 ` Vineet Gupta
2021-05-17 16:59 ` Yann E. MORIN [this message]
2021-05-10 18:00 ` [Buildroot] [PATCH v3 4/4] lmbench: lat_rpc: fix stray pointer Vineet Gupta
2021-05-17 20:09 ` Yann E. MORIN
2021-05-20 8:41 ` Peter Korsgaard
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=20210517165905.GB2506@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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