From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] procps-ng: Fix installation and take precedence over busybox
Date: Wed, 10 Sep 2014 23:04:24 +0200 [thread overview]
Message-ID: <20140910230424.14192582@free-electrons.com> (raw)
In-Reply-To: <1410359406-49326-2-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Wed, 10 Sep 2014 15:30:06 +0100, Vicente Olivert Riera wrote:
> Currently procps-ng binaries are installed under $(TARGET_DIR)/usr/usr
> instead of $(TARGET_DIR)/usr, which would be the expected. This is
> caused because the default value of the --exec-prefix configure option
> is /usr, and Buildroot always adds --prefix=/usr to the configure
> option. We fix this by setting --exec-prefix to an empty value.
>
> At the same time we make sure the procps-ng binaries have precedence
> over the busybox ones.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Reviewed-by: Markos.Chandras <Markos.Chandras@imgtec.com>
> ---
> package/procps-ng/procps-ng.mk | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-10 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 14:30 [Buildroot] [PATCH 1/2] coreutils: Do not install uptime Vicente Olivert Riera
2014-09-10 14:30 ` [Buildroot] [PATCH 2/2] procps-ng: Fix installation and take precedence over busybox Vicente Olivert Riera
2014-09-10 21:04 ` Thomas Petazzoni [this message]
2014-09-13 21:56 ` Peter Korsgaard
2014-09-10 20:45 ` [Buildroot] [PATCH 1/2] coreutils: Do not install uptime Thomas Petazzoni
2014-09-11 9:13 ` Vicente Olivert Riera
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=20140910230424.14192582@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 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.