From: g4 at novadsp.com <g4@novadsp.com>
To: buildroot@busybox.net
Subject: [Buildroot] B3+external kernel: not quite sure how to make these pieces fit ...
Date: Wed, 24 Jun 2015 20:06:35 +0100 [thread overview]
Message-ID: <066601d0aeb0$e445c840$acd158c0$@novadsp.com> (raw)
Want to automate building kernel and filesystem for Beaglebones.
The kernel itself is the mainline 4.x with a set of patches applied from
Robert Nelson's (RCN) GIT repo.
Problem is that there is no mechanism for file system construction/
packaging. Obviously Buildroot to the rescue here.
I thought I'd start by trying to get BR to use the existing external
toolchain - specifying 'toolchain path' as
'~/rcn/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux'
But this fails with 'External toolchain uses the unsuported OABI'. There is
an old reference to this here:
http://git.buildroot.net/buildroot/commit/?id=b2e88073dbf05faa47475bf96d5ccf
8a45906a3c
I don't see any conflict with the target settings. Is there a solution or is
this a more fundamental/complex issue?
This obviously begs the question of how the externally built kernel gets
into the BR mix but I'll leave that for next time.
Thx++
--------------------snip--------------------
Target Architecture (ARM (little endian)) --->
x x
x x Target Binary Format (ELF) --->
x x
x x Target Architecture Variant (cortex-A8) --->
x x
x x Target ABI (EABIhf) --->
x x
x x Floating point strategy (VFPv3-D16) --->
x x
x x ARM instruction set (ARM) --->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150624/2eadb813/attachment.html>
next reply other threads:[~2015-06-24 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 19:06 g4 at novadsp.com [this message]
2015-06-24 21:05 ` [Buildroot] B3+external kernel: not quite sure how to make these pieces fit Arnout Vandecappelle
2015-06-25 11:08 ` g4 at novadsp.com
2015-06-25 23:06 ` Arnout Vandecappelle
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='066601d0aeb0$e445c840$acd158c0$@novadsp.com' \
--to=g4@novadsp.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