From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using external toolchain
Date: Tue, 23 Dec 2014 20:49:49 +0100 [thread overview]
Message-ID: <20141223204949.58a5ff74@free-electrons.com> (raw)
In-Reply-To: <CALo-6+gkiNsQ-3151+wsfqGsr9tjOhyQGGveKU7ZwsYkX9RMqw@mail.gmail.com>
Dear Charles Krinke,
On Tue, 23 Dec 2014 10:32:11 -0800, Charles Krinke wrote:
> loginutils/passwd.c: In function 'passwd_main':
> loginutils/passwd.c:93:16: error: storage size of 'rlimit_fsize' isn't known
> struct rlimit rlimit_fsize;
> ^
> loginutils/passwd.c:180:2: warning: implicit declaration of function
> 'setrlimit' [-Wimplicit-function-declaration]
> setrlimit(RLIMIT_FSIZE, &rlimit_fsize);
> ^
> loginutils/passwd.c:180:12: error: 'RLIMIT_FSIZE' undeclared (first use in
> this function)
Too old Busybox. Please make sure you have a version that has at least
http://git.buildroot.net/busybox/commit/loginutils/passwd.c?id=c5fe9f7b723f949457263ef8e22ab807d5b549ce.
You should *really* consider updating. By using a 3 years old
Buildroot, with 3 years old upstream software, you are going to face
zillions of issues that have already been fixed since 2+ years, like
this passwd.c build problem. This very problem is an excellent
illustration of why sticking with such old versions is a bad decision.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-12-23 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 19:33 [Buildroot] Using external toolchain Charles Krinke
2014-12-20 15:10 ` Thomas Petazzoni
2014-12-23 18:32 ` Charles Krinke
2014-12-23 19:49 ` Thomas Petazzoni [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=20141223204949.58a5ff74@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