Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] odhcploc: new package
Date: Sun, 17 Aug 2014 21:34:15 +0200	[thread overview]
Message-ID: <20140817213415.5ea4809a@free-electrons.com> (raw)
In-Reply-To: <1407607617-18039-1-git-send-email-bos@je-eigen-domein.nl>

Dear Floris Bos,

On Sat,  9 Aug 2014 20:06:57 +0200, Floris Bos wrote:
> Adds odhcploc, a network utility to scan for (rogue) DHCP servers.
> 
> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>

Thanks, I've applied the patch to the next branch, after doing a few
changes, see below.

> +ODHCPLOC_VERSION = 20111021
> +ODHCPLOC_SOURCE = odhcploc-$(ODHCPLOC_VERSION).tar.gz

Line removed, after the suggestion from Thomas DS.

> +ODHCPLOC_SITE = http://downloads.sourceforge.net/project/odhcploc/$(ODHCPLOC_VERSION)
> +ODHCPLOC_LICENSE = ISC
> +ODHCPLOC_LICENSE_FILES = COPYING
> +
> +define ODHCPLOC_BUILD_CMDS
> +     $(MAKE) CC="$(TARGET_CC)" LD="$(TARGET_LD)" -C $(@D) all

Used tab for indentation instead of spaces, and replaced CC=.. LD=.. by
$(TARGET_CONFIGURE_OPTS).

> +define ODHCPLOC_INSTALL_TARGET_CMDS
> +     $(INSTALL) -D -m 0755 $(@D)/odhcploc $(TARGET_DIR)/usr/bin/odhcploc

Used 'make install' instead of manually doing the installation.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-08-17 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 18:06 [Buildroot] [PATCH 1/1] odhcploc: new package Floris Bos
2014-08-10  7:03 ` Thomas De Schampheleire
2014-08-17 19:34 ` Thomas Petazzoni [this message]
2014-08-17 20:51   ` Floris Bos
2014-08-18  7:46     ` Thomas Petazzoni

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=20140817213415.5ea4809a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox