From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bare metal toolchain support?
Date: Wed, 23 Nov 2016 13:06:36 +0100 [thread overview]
Message-ID: <20161123130636.5b362a27@free-electrons.com> (raw)
In-Reply-To: <CAM+bi4vNKMBr0Dv9_-rsQzU_kPNrze7o9_EcSEA--g2UCVCfzg@mail.gmail.com>
Hello,
On Wed, 23 Nov 2016 12:20:35 +0100, Alvaro Gamez wrote:
> errno.c:6:19: fatal error: reent.h: No such file or directory
> #include <reent.h>
>
> This reent.h header doesn't exist in the toolchain built by buildroot, but
> it exists on Xilinx's:
reent.h is a newlib-specific header, which indeed will only exist on
bare-metal toolchains that use newlib. However, it's surprising that
bootloader code includes reent.h: this file defines the reentrant
variant of a number of system-level functions (close, stat, etc.). Which
doesn't make a lot of sense in a bootloader.
Perhaps it is not really used? I guess, you'll have to hack things
a bit to get them to build.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-23 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 9:49 [Buildroot] Bare metal toolchain support? Alvaro Gamez
2016-11-23 10:35 ` Thomas Petazzoni
2016-11-23 11:20 ` Alvaro Gamez
2016-11-23 12:06 ` Thomas Petazzoni [this message]
2016-11-23 12:16 ` Alvaro Gamez
2016-11-23 14:49 ` Alvaro Gamez
2016-11-23 16:44 ` Alvaro Gamez
2016-11-24 20:41 ` Arnout Vandecappelle
2016-11-25 7:54 ` Alvaro Gamez
2016-11-26 13:49 ` 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=20161123130636.5b362a27@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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