All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Chrony time synchronization (chronyc and chronyd)
Date: Sat, 27 Mar 2010 13:00:22 +0100	[thread overview]
Message-ID: <20100327120022.GD21542@excalibur.local> (raw)
In-Reply-To: <4AF1C9D3.2020604@cam.ac.uk>

Hello.

On Wed, 2009-11-04 at 18:37, Jonathan Cameron wrote:
> 
> Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
> Unfortunately this package uses a hand rolled set of build scripts.
> The maintainers are happy to add fixes to any problems but are not
> keen on moving over to autotools. I don't get the impression many
> people cross compile this one! That is a shame because it is very
> useful with wireless sensor nodes.
> 
> There are a few nasty tests in the configure script that may well
> cause problems in cross compiles when the host is not also linux based.
> 
> I will work on getting these fixed at source, but it may take a while
> hence submission of this recipe in the meantime.
> 
> The reason this is the git version is recent patches to ensure
> that the LDPATH variable was not ignored in linking.
> 
> This recipe includes some convenient scripts and blank config
> files needed to get it up and running easily.

Applied and pushed. I have rewritten the subject line to be more like what we
expect in OE. If you have progress on having a saner upstream build system we
would appreciate if we could make this recipe a bit cleaner. Thanks.

regards
Stefan Schmidt



      reply	other threads:[~2010-03-27 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 18:37 [PATCH] Chrony time synchronization (chronyc and chronyd) Jonathan Cameron
2010-03-27 12:00 ` Stefan Schmidt [this message]

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=20100327120022.GD21542@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.