From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot compilation error
Date: Fri, 24 Jul 2020 21:14:45 +0200 [thread overview]
Message-ID: <20200724211445.536ef09b@gmx.net> (raw)
In-Reply-To: <CAKBF_5rzmSryuzdhs7oSHobxTVNYL_H7Lj04uxjZY+6UaNK=nA@mail.gmail.com>
Hello Billa,
On Fri, 24 Jul 2020 12:16:16 +0530, Billa Surendra <billa.iitmadras@gmail.com> wrote:
> Dear all,
>
> I am getting errors while compiling buildroot for riscv architecture. Can
> anyone please help me regarding this?.
>
> Error:
>
> fseeko.c: In function 'rpl_fseeko':
> fseeko.c:109:4: error: #error "Please port gnulib fseeko.c to your
> platform! Loo k at the code in fseeko.c, then report this to
> bug-gnulib."
> 109 | #error "Please port gnulib fseeko.c to your platform! Look at the
> code in fseeko.c, then report this to bug-gnulib."
> | ^~~~~
> make[5]: *** [Makefile:1842: fseeko.o] Error 1
> make[5]: *** Waiting for unfinished jobs....
> freadahead.c: In function 'freadahead':
> freadahead.c:91:3: error: #error "Please port gnulib freadahead.c to your
> platfo rm! Look at the definition of fflush, fread, ungetc on your
> system, then report this to bug-gnulib."
> 91 | #error "Please port gnulib freadahead.c to your platform! Look at
> the d efinition of fflush, fread, ungetc on your system, then
> report this to bug-gnuli b."
Mind to provide a .config (or defconfig) file? Which buildroot version?
Regards,
Peter
>
> Thanks and regards
> Billa Surendra
next prev parent reply other threads:[~2020-07-24 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 6:46 [Buildroot] buildroot compilation error Billa Surendra
2020-07-24 19:14 ` Peter Seiderer [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-14 12:22 rajesh gandla
2014-05-14 13:52 ` Thomas Petazzoni
2008-03-18 10:57 [Buildroot] Buildroot " Reinier Coetzer
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=20200724211445.536ef09b@gmx.net \
--to=ps.report@gmx.net \
--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