Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/7] dhcpcd: install binary to /sbin
Date: Fri, 7 Nov 2014 13:42:32 +0000	[thread overview]
Message-ID: <545CCC48.9070106@imgtec.com> (raw)
In-Reply-To: <1415281013-1077-4-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On 11/06/2014 01:36 PM, Gustavo Zacarias wrote:
> Debian ifupdown expects dhcpcd to be in /sbin rather than /usr/sbin
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/dhcpcd/dhcpcd.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/dhcpcd/dhcpcd.mk b/package/dhcpcd/dhcpcd.mk
> index f4b821a..60ac129 100644
> --- a/package/dhcpcd/dhcpcd.mk
> +++ b/package/dhcpcd/dhcpcd.mk
> @@ -37,7 +37,7 @@ endef
>  
>  define DHCPCD_INSTALL_TARGET_CMDS
>  	$(INSTALL) -D -m 0755 $(@D)/dhcpcd \
> -		$(TARGET_DIR)/usr/sbin/dhcpcd
> +		$(TARGET_DIR)/sbin/dhcpcd
>  	$(INSTALL) -D -m 0644 $(@D)/dhcpcd.conf \
>  		$(TARGET_DIR)/etc/dhcpcd.conf
>  	$(INSTALL) -D -m 0755 $(@D)/dhcpcd-run-hooks \
> 

Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

Compile test on MIPS architecture plus checking the files are installed
in target and have been built for the right architecture:

$ file output/target/sbin/dhcpcd
output/target/sbin/dhcpcd: ELF 32-bit MSB executable, MIPS, MIPS32 rel2
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
2.6.16, with unknown capability 0x41000000 = 0xf676e75, with unknown
capability 0x10000 = 0x70403, stripped

Best regards,
-- 
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com

  reply	other threads:[~2014-11-07 13:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 13:36 [Buildroot] [PATCH 0/7] [RFC] systemV init without busybox series Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 1/7] skeleton/S40network: tweak for debian ifupdown Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 2/7] package/uclibc: enable wordexp Gustavo Zacarias
2014-11-06 17:22   ` Thomas Petazzoni
2014-11-06 17:25     ` Gustavo Zacarias
2014-11-06 17:45       ` Thomas Petazzoni
2014-11-06 17:48         ` Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 3/7] dhcpcd: install binary to /sbin Gustavo Zacarias
2014-11-07 13:42   ` Vicente Olivert Riera [this message]
2014-11-06 13:36 ` [Buildroot] [PATCH 4/7] dhcpcd: bump to version 6.6.0 Gustavo Zacarias
2014-11-07 13:42   ` Vicente Olivert Riera
2014-11-06 13:36 ` [Buildroot] [PATCH 5/7] dash: bump to 0.5.8-2 Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 6/7] debianutils: new package Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 7/7] ifupdown: " Gustavo Zacarias
2014-11-06 18:00   ` Danomi Manchego
2014-11-06 18:10     ` Gustavo Zacarias
2014-11-06 18:12   ` Thomas Petazzoni
2014-11-06 18:34     ` Gustavo Zacarias
2014-11-06 17:24 ` [Buildroot] [PATCH 0/7] [RFC] systemV init without busybox series Thomas Petazzoni
2014-11-06 17:32   ` Gustavo Zacarias
2014-11-07  9:12     ` Károly Kasza
2014-11-07 10:07       ` Gustavo Zacarias

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=545CCC48.9070106@imgtec.com \
    --to=vincent.riera@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox