From: Ron Eggler <ron.eggler@gmail.com>
To: bug-gnulib@gnu.org
Subject: port freadahead.c & fseeko.c
Date: Wed, 23 Dec 2020 13:56:20 -0800 [thread overview]
Message-ID: <CAHxBh_T5gn6FhzLpxLaVYqt8aLsVM1fhLO8G=0zjL-WkyM_Dyg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Hi,
I'm attemprting to compile an image for a DIGI UL6 SBC and am getting the
following error:
../../m4-1.4.17/lib/freadahead.c: In function ‘freadahead’:
../../m4-1.4.17/lib/freadahead.c:91:3: error: #error "Please port gnulib
freadahead.c to your platform! 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 definition of fflush, fread, ungetc on your system, then report this to
bug-gnulib."
| ^~~~~
gcc -I. -I../../m4-1.4.17/lib
-isystem/home/ron/workspace/tmp/sysroots/x86_64-linux/usr/include
-isystem/home/ron/workspace/tmp/sysroots/x86_64-linux/usr/include -O2
-pipe -c -o vasprintf.o ../../m4-1.4.17/lib/vasprintf.c
ERROR: oe_runmake failed
make[3]: *** [Makefile:1842: freadahead.o] Error 1
make[3]: *** Waiting for unfinished jobs....
../../m4-1.4.17/lib/fseeko.c: In function ‘rpl_fseeko’:
../../m4-1.4.17/lib/fseeko.c:109:4: error: #error "Please port gnulib
fseeko.c to your platform! Look 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."
How can I patch these files to work with my platform?
Ron
[-- Attachment #2: Type: text/html, Size: 1501 bytes --]
next reply other threads:[~2020-12-23 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 21:56 Ron Eggler [this message]
2020-12-24 0:17 ` port freadahead.c & fseeko.c Paul Eggert
2020-12-28 17:39 ` Ron Eggler
2020-12-28 19:16 ` Paul Eggert
2020-12-28 21:34 ` Ron Eggler
2020-12-28 22:08 ` Bruno Haible
2020-12-29 2:32 ` Ron Eggler
2020-12-29 3:48 ` Bruno Haible
2020-12-24 1:38 ` Bruno Haible
2020-12-24 1:59 ` Ron Eggler
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHxBh_T5gn6FhzLpxLaVYqt8aLsVM1fhLO8G=0zjL-WkyM_Dyg@mail.gmail.com' \
--to=ron.eggler@gmail.com \
--cc=bug-gnulib@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).