From: Ron Eggler <ron.eggler@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: port freadahead.c & fseeko.c
Date: Mon, 28 Dec 2020 09:39:14 -0800 [thread overview]
Message-ID: <e4ee4689-4a29-02ee-2cf6-00543e5f9b5c@gmail.com> (raw)
In-Reply-To: <a17d2573-342a-34ce-8cf6-aeafaac27fd4@cs.ucla.edu>
Paul,
Mind, I'm I am cross compiling
So I cd-ed to:
/home/ron/novax-prs/tmp/work/x86_64-linux/m4-native/1.4.17-r0/build/lib/
and opened: ../../m4-1.4.17/lib/fseeko.c
but funny enough, I cannot find any function that is called "rpl_fseeko"
even though the error states:
| make[3]: Entering directory
'/home/ron/novax-prs/tmp/work/x86_64-linux/m4-native/1.4.17-r0/build/lib'
| gcc -I. -I../../m4-1.4.17/lib
-isystem/home/ron/novax-prs/tmp/sysroots/x86_64-linux/usr/include
-isystem/home/ron/novax-prs/tmp/sysroots/x86_64-linux/usr/include -O2
-pipe -c -o freadahead.o ../../m4-1.4.17/lib/freadahead.c
| gcc -I. -I../../m4-1.4.17/lib
-isystem/home/ron/novax-prs/tmp/sysroots/x86_64-linux/usr/include
-isystem/home/ron/novax-prs/tmp/sysroots/x86_64-linux/usr/include -O2
-pipe -c -o fseeko.o ../../m4-1.4.17/lib/fseeko.c
| ../../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."
On 2020-12-23 4:17 p.m., Paul Eggert wrote:
> On 12/23/20 1:56 PM, Ron Eggler wrote:
>> How can I patch these files to work with my platform?
>
> Look in your stdio.h (commonly /usr/include/stdio.h), and the files it
> includes, to see how it defines ungetc etc. Then use that knowledge to
> update lib/freadahead.c and lib/fseeko.c. It'll require some expertise
> in low-level C hacking.
next prev parent reply other threads:[~2020-12-28 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 21:56 port freadahead.c & fseeko.c Ron Eggler
2020-12-24 0:17 ` Paul Eggert
2020-12-28 17:39 ` Ron Eggler [this message]
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=e4ee4689-4a29-02ee-2cf6-00543e5f9b5c@gmail.com \
--to=ron.eggler@gmail.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).