bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: port freadahead.c & fseeko.c


From: Ron Eggler
Subject: Re: port freadahead.c & fseeko.c
Date: Mon, 28 Dec 2020 13:34:32 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0


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.

I'm having troubles with finding the correct definition, when I grep the sources for ungetc I get the following:

x86_64-linux$ grep -rn --include \*.h ungetc
m4-native/1.4.17-r0/m4-1.4.17/lib/stdio-impl.h:65:      struct  __sbuf _ub; /* ungetc buffer */
m4-native/1.4.17-r0/m4-1.4.17/lib/freadahead.h:23:   source and the bytes that have been pushed back through 'ungetc'.
m4-native/1.4.17-r0/build/lib/config.h:96:/* Define to 1 if ungetc is broken when used on arbitrary bytes. */
binutils-native/2.27-r0/git/zlib/zconf.h:91:#    define gzungetc              z_gzungetc
binutils-native/2.27-r0/git/zlib/zlib.h:1400:ZEXTERN int ZEXPORT gzungetc OF((int c, gzFile file));
binutils-native/2.27-r0/git/zlib/zlib.h:1404:   gzungetc() returns the character pushed, or -1 on failure.  gzungetc() will
binutils-native/2.27-r0/git/zlib/zlib.h:1406:   yet.  If gzungetc is used immediately after gzopen or gzdopen, at least the
ron@ENGDEV:~/novax-prs/tmp/work/x86_64-linux$

and I'm not exactly sure how I should adjust the definitions in fseeko.c & freadaheaed.c accordingly.

As for:

On 12/28/20 9:39 AM, Ron Eggler wrote:

I cannot find any function that is called "rpl_fseeko"

Presumably an earlier "#define fseeko rpl_fseeko" means that when you see a definition of the fseeko function, it's really defining rpl_fseeko.


That's correct, I missed to see this!


Thanks for all!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]