From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] make Error
Date: Fri, 2 Jun 2017 09:49:44 +0200 [thread overview]
Message-ID: <20170602094944.4dd492eb@free-electrons.com> (raw)
In-Reply-To: <CAN=nCKAPW+_Ns40xKCiDmFu+pit8k_nP_onGS9fNwNyxem5KeA@mail.gmail.com>
Hello,
First of all, thanks for your bug report.
On Thu, 1 Jun 2017 23:36:25 +0530, Saurabh Mishra wrote:
> I'm trying to build (*build root-2015.05-rc2) *but when I'm running make
> command its giving error in* /config/host-linux.c:215:43: error:
> 'SSIZE_MAX' was not declared in this scope* , i tried to pass hardcoded
> integer value instead of SSIZE_MAX but that is also not working , your help
> would be appreciated.
The information provided in your e-mail is not sufficient to help you.
We need to have:
- The last ~100 lines of the build output
- The full Buildroot .config file
Also, make sure this error is reproducible after doing a full rebuild
(i.e "make clean all"). Please read
http://nightly.buildroot.org/manual.html#full-rebuild.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-02 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 18:06 [Buildroot] make Error Saurabh Mishra
2017-06-02 7:49 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-18 8:54 [Buildroot] Make Error suhas dumbhare
2009-01-14 23:17 [Buildroot] Make error Jerry Zhang
2009-01-14 23:27 ` Jerry Zhang
2008-08-31 0:50 Steven Woody
2008-08-31 1:59 ` Steven Woody
2008-08-31 6:23 ` Peter Korsgaard
2008-08-31 7:34 ` Steven Woody
2008-08-31 9:13 ` Steven Woody
2008-09-02 13:29 ` Peter Korsgaard
2008-09-02 15:03 ` Steven Woody
2007-08-23 19:16 Terry Bolinger
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=20170602094944.4dd492eb@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