Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Moore <will.moore@beraninstruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] Method of moving to new releases of buildroot
Date: Mon, 10 May 2010 10:24:52 +0100	[thread overview]
Message-ID: <92845763320042419CF46BEE34059A68@AP366> (raw)
In-Reply-To: 87bpcubgz5.fsf@macbook.be.48ers.dk

As a point of process, how is it intended that a user moves to a new version
of buildroot?

I tried making 2010.05 rc1 with my 2010.02 buildroot, kernel and busybox
.config files from 2010.02 (just accepting default new configuration
options) but found the build failed due to the previously mentioned problem
with uclibc and usleep when building gdbserver for the target.

Please can those with more experience of buildroot let me know if what I did
was a) daft and bound to fail or b) acceptable practice but failed in this
instance.  What do others do?

Thanks,



Will

      parent reply	other threads:[~2010-05-10  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 13:43 [Buildroot] uclibc .9.31 & usleep Sagaert Johan
2010-05-05 13:44 ` Peter Korsgaard
2010-05-05 14:00   ` Will Moore
2010-05-10  9:24   ` Will Moore [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=92845763320042419CF46BEE34059A68@AP366 \
    --to=will.moore@beraninstruments.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