From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Why is libbsd limited to ARM, x86 and x86_64?
Date: Thu, 4 Feb 2016 01:00:14 +0100 [thread overview]
Message-ID: <56B2948E.2090805@mind.be> (raw)
In-Reply-To: <1734711132.950514.1454525438621.JavaMail.zimbra@datacom.ind.br>
[Please don't top-post]
On 03-02-16 19:50, Carlos Santos wrote:
> Two questions, first:
>
> 1. Is it enough to build for quemu boards?
Sure. I don't think runtime testing is really needed, except maybe for powerpc.
>
> 2. I'm absolutely ignorant about nios2. What defconfig should I use to build for it?
Hm, looks like we don't have a nios2 defconfig... But you can do a very quick
build-test by setting arch to nios2 and selecting the Sourcery toolchain.
Regards,
Arnout
>
> Carlos Santos (Casantos)
> DATACOM, P&D
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-04 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 15:30 [Buildroot] Why is libbsd limited to ARM, x86 and x86_64? Carlos Santos
2016-02-02 21:09 ` Arnout Vandecappelle
2016-02-03 15:39 ` Carlos Santos
2016-02-03 18:50 ` Carlos Santos
2016-02-04 0:00 ` Arnout Vandecappelle [this message]
2016-02-04 5:21 ` Baruch Siach
2016-02-04 12:22 ` Carlos Santos
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=56B2948E.2090805@mind.be \
--to=arnout@mind.be \
--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.