All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH v2] openntpd: Add recipe for building OpenNTPD
Date: Wed, 12 Feb 2014 14:38:14 -0500	[thread overview]
Message-ID: <20140212193813.GO4346@edge> (raw)
In-Reply-To: <1392230029-12829-1-git-send-email-sam.nelson@ti.com>

On Wed, Feb 12, 2014 at 01:33:49PM -0500, Sam Nelson wrote:
> - OpenNTPD is a open source implementation of Network time protocol
> 
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> 
> ---
> Changes from previous patch
> * Moved to recipes-connectivity
> * Removed redundant setting of STAGING_KERNEL_DIR
> ---
> ---
>  .../openntpd/openntpd_3.9p1.bb                     |   26 ++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100755 meta-arago-extras/recipes-connectivity/openntpd/openntpd_3.9p1.bb
> 
> diff --git a/meta-arago-extras/recipes-connectivity/openntpd/openntpd_3.9p1.bb b/meta-arago-extras/recipes-connectivity/openntpd/openntpd_3.9p1.bb
> new file mode 100755
> index 0000000..ca090e4
> --- /dev/null
> +++ b/meta-arago-extras/recipes-connectivity/openntpd/openntpd_3.9p1.bb
> @@ -0,0 +1,26 @@
> +DESCRIPTION = "OpenNTPD is a FREE, easy to use implementation of the \
> +Network Time Protocol."
> +HOMEPAGE = "http://www.openntpd.org/"
> +SECTION = "console/network"
> +LICENSE = "BSD ISC"
> +LIC_FILES_CHKSUM = "file://LICENCE;md5=4b4f5158007cc97e6b0e2325bb99854a"
> +
> +DEPENDS += "virtual/kernel"
> +PR = "r0"
> +
> +SRC_URI = "http://mirror.ece.vt.edu/pub/OpenBSD/OpenNTPD/${P}.tar.gz"
> +
> +S = "${WORKDIR}/openntpd-${PV}"
> +EXTRA_OECONF = "--disable-strip"
> +inherit autotools
> +
> +LDFLAGS += "-lrt"
> +CFLAGS += "-DTI_ADD_SUPPORT_HW_TIMESTAMPING"
> +CPPFLAGS = "-I${STAGING_KERNEL_DIR}/include"
> +CPPFLAGS += "-I${STAGING_KERNEL_DIR}/arch/arm/include"

Sam, I keep seeing you passing staged kernel location to user-space apps and 
daemons and I'm growing suspicious that it's not really needed... Both 
openntpd and linuxptp should be buildable as is w/o needing to have access to 
the staged kernel. Unless I'm missing something and they do use kernel headers 
directly (not libc provided) and you have those headers modified for your 
platform... Can you please elaborate here? Thanks.


> +EXTRA_OECONF += "CPPFLAGS="${CPPFLAGS}" LDFLAGS="${LDFLAGS}" CFLAGS="${CFLAGS}" \
> +                 --with-privsep-user=root --with-privsep-path=/${prefix}"
> +
> +SRC_URI[md5sum] = "afc34175f38d08867c1403d9008600b3"
> +SRC_URI[sha256sum] = "83dd7c1e8ec8b4567afe49af539271b5a73562fb7a3ca51df73eccba89ec8c49"
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2014-02-12 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 18:33 [PATCH v2] openntpd: Add recipe for building OpenNTPD Sam Nelson
2014-02-12 19:38 ` Denys Dmytriyenko [this message]
2014-02-13  4:02   ` Nelson, Sam
2014-02-14 15:27   ` Nelson, Sam
2014-02-14 19:02     ` Denys Dmytriyenko
2014-02-27 15:49       ` Nelson, Sam
2014-02-27 17:59         ` Denys Dmytriyenko

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=20140212193813.GO4346@edge \
    --to=denys@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=sam.nelson@ti.com \
    /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.