All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: buildroot@busybox.net
Subject: [Buildroot] config choices in building for beaglebone black (BBB)?
Date: Thu, 16 Apr 2015 09:03:59 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1504160857510.20888@localhost> (raw)


  anyone who uses buildroot to build for a BBB will probably know the
answers to this instantly.

  did a "git clone" of buildroot, and did nothing more than:

  $ make beaglebone_defconfig
  $ make

so, basically, all the defaults, worked fine. so now i'm looking at my
config options and want to know how far i can push a BBB build to the
bleeding edge, and about the BBB defaults.

  first, i notice that the default build for BBB uses uClibc rather
than glibc, which is easy enough to adjust, but i'm curious as to why
something like a BBB doesn't have glibc as the default C library to
use.

  also, for bleeding edge, can anyone verify whether i'm safe pushing
the versions of everything right to the latest? you know:

  * kernel 4.0.x
  * glibc 2.21
  * binutils 2.25
  * gcc 4.9.x

and so on, and so on. any other BBB issues anyone wants to warn me
about before i go charging off in that direction? thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2015-04-16 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 13:03 Robert P. J. Day [this message]
2015-04-16 21:31 ` [Buildroot] config choices in building for beaglebone black (BBB)? Arnout Vandecappelle
2015-04-20 21:36   ` Peter Korsgaard

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=alpine.LFD.2.11.1504160857510.20888@localhost \
    --to=rpjday@crashcourse.ca \
    --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.