From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] aiccu: new package
Date: Mon, 2 Sep 2013 10:57:10 +0200 [thread overview]
Message-ID: <20130902105710.1d665e8f@skate> (raw)
In-Reply-To: <1378071216-19697-2-git-send-email-rommel@layer-7.net>
Dear Michael Rommel,
Thanks a lot for your continuous effort with those patches. I now see
that you managed to use 'git rebase -i' and generate a very nice patch
series!
On Sun, 1 Sep 2013 23:33:35 +0200, Michael Rommel wrote:
> diff --git a/package/aiccu/Config.in b/package/aiccu/Config.in
> new file mode 100644
> index 0000000..008ada7
> --- /dev/null
> +++ b/package/aiccu/Config.in
> @@ -0,0 +1,24 @@
> +config BR2_PACKAGE_AICCU
> + bool "aiccu"
> + depends on BR2_INET_IPV6
> + depends on BR2_USE_WCHAR
> + select BR2_PACKAGE_GNUTLS
> + help
> + SixXS Automatic IPv6 Connectivity Client Utility
> +
> + AICCU (Automatic IPv6 Connectivity Client Utility) makes it
> + easy for users to get IPv6 connectivity. After having
> + requested an account, tunnel and optionally a subnet, AICCU
> + can be used to automatically configure the tunnel. AICCU
> + supports TIC (Tunnel Information & Control protocol), which it
> + uses for retrieving the tunnel configuration information,
> + AYIYA, which allows tunnels to be created even behind
> + firewalls and NAT's.
> +
> + http://www.sixxs.net/tools/aiccu/
> +
> +comment "aiccu requires a toolchain with IPv6 support"
> + depends on !BR2_INET_IPV6
> +
> +comment "aiccu requires a toolchain with WCHAR support"
> + depends on !BR2_USE_WCHAR
We generally have only one comment for both. See examples in other
packages.
> diff --git a/package/aiccu/aiccu.mk b/package/aiccu/aiccu.mk
> new file mode 100644
> index 0000000..da3cc3b
> --- /dev/null
> +++ b/package/aiccu/aiccu.mk
> @@ -0,0 +1,25 @@
> +################################################################################
> +#
> +# aiccu
> +#
> +################################################################################
> +
> +AICCU_VERSION = 20070115
> +AICCU_SOURCE = aiccu_$(AICCU_VERSION).tar.gz
> +AICCU_SITE = http://www.sixxs.net/archive/sixxs/aiccu/unix/
> +AICCU_LICENSE = SixXS License, concise redistribution license
> +AICCU_LICENSE_FILES = doc/LICENSE
> +AICCU_DEPENDENCIES = gnutls
> +
> +define AICCU_BUILD_CMDS
> + $(MAKE) CC="$(TARGET_CC)" LD="$(TARGET_LD)" -C $(@D) all
You could use:
$(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) all
TARGET_CONFIGURE_OPTS contains the definitions of CC, LD, CFLAGS,
LDFLAGS, and more.
> +define AICCU_INSTALL_TARGET_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/unix-console/aiccu $(TARGET_DIR)/usr/sbin
> + $(INSTALL) -D -m 0644 $(@D)/doc/aiccu.conf $(TARGET_DIR)/etc
> + $(INSTALL) -D -m 0755 $(@D)/doc/aiccu.init \
> + $(TARGET_DIR)/usr/sbin/S90aiccu
> +endef
Either use 'make install' as Thomas suggested, or if it's really not
possible, you need to make the second argument the complete filename,
not only the destination directory.
Moreover, the init script must be installed in /etc/init.d, not
in /usr/sbin. And finally, it should not be installed manually, but
instead should use the INIT_SYSV mechanism. See the Buildroot manual,
which states:
LIBFOO_INSTALL_INIT_SYSV and LIBFOO_INSTALL_INIT_SYSTEMD list the
actions to install init scripts either for the systemV-like init
systems (busybox, sysvinit, etc.) or for the systemd units. These
commands will be run only when the relevant init system is installed
(i.e. if systemd is selected as the init system in the configuration,
only LIBFOO_INSTALL_INIT_SYSTEMD will be run).
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-02 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 21:33 [Buildroot] [PATCH 1/3] knock: new package Michael Rommel
2013-09-01 21:33 ` [Buildroot] [PATCH 2/3] aiccu: " Michael Rommel
2013-09-02 8:28 ` Thomas De Schampheleire
2013-09-02 8:57 ` Thomas Petazzoni [this message]
2013-09-02 23:49 ` Michael Rommel
2013-09-01 21:33 ` [Buildroot] [PATCH 3/3] python-pyzmq: " Michael Rommel
2013-09-02 8:24 ` Thomas De Schampheleire
2013-09-02 15:55 ` Arnout Vandecappelle
2013-09-03 18:04 ` Michael Rommel
2013-09-03 21:30 ` Arnout Vandecappelle
2013-09-08 12:07 ` [Buildroot] [PATCH 1/3] knock: " Thomas De Schampheleire
2013-09-08 12:08 ` Thomas De Schampheleire
[not found] ` <E9670545-EE12-445D-A15C-C0C3E4A4116A@layer-7.net>
2013-09-08 14:09 ` Michael Rommel
2013-09-08 14:32 ` Thomas De Schampheleire
2013-09-10 20:58 ` Arnout Vandecappelle
2013-09-15 18:18 ` 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=20130902105710.1d665e8f@skate \
--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