All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] chrony: new package
Date: Mon, 06 May 2013 14:01:52 -0500	[thread overview]
Message-ID: <1367866912.2177.14.camel@doorstop.aus.2wire.com> (raw)
In-Reply-To: <20130506194935.6340c5a8@skate>

On Mon, 2013-05-06 at 19:49 +0200, Thomas Petazzoni wrote:
> Dear Nathan Lynch,
> 
> On Mon, 06 May 2013 12:42:36 -0500, Nathan Lynch wrote:
> 
> > > Also, did you check that this program indeed builds with a minimal
> > > uClibc toolchain (no thread, no wchar, no locale, no nothing) ?
> > 
> > Sorry, no, that was sloppy of me.  I will do so for v2 and try to
> > better specify the package's needs and dependencies.  I'd be happy to
> > try any configs you'd care to point out...
> 
> You can try a very minimal build: no thread, no wchar, no locale, no
> C++, no nothing. If it builds, you're all set. If your package doesn't
> build, then something is missing.
> 
> If you don't want to spend too much time building toolchains, you can
> use:
> 
>  http://autobuild.buildroot.org/toolchains/tarballs/br-arm-basic.tar.bz2
>  as an external toolchain that is minimal (no C++, no wchar, no locale,
>  no largefile, etc. but it has thread support)
> 
>  http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-nothread.tar.bz2
>  as an external that has everything (C++, wchar, locale, largefile,
>  etc.), but doesn't has thread support.
> 
> If your package builds with both, then normally you should be all set.

Thank you for this guidance.  I verified that the package builds with
both of these and found no issues (I did realize it needs MMU, however).
I will do similarly for future package submissions.

v2 with the rest of your feedback addressed on its way.

  reply	other threads:[~2013-05-06 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 16:12 [Buildroot] [PATCH] chrony: new package Nathan Lynch
2013-05-06 17:20 ` Thomas Petazzoni
2013-05-06 17:42   ` Nathan Lynch
2013-05-06 17:49     ` Thomas Petazzoni
2013-05-06 19:01       ` Nathan Lynch [this message]
2013-05-06 20:00         ` 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=1367866912.2177.14.camel@doorstop.aus.2wire.com \
    --to=ntl@pobox.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 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.