From: Ron Eggler <ron.eggler@gmail.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: port freadahead.c & fseeko.c
Date: Mon, 28 Dec 2020 18:32:44 -0800 [thread overview]
Message-ID: <6072c1ba-eddf-5fcf-676c-3ce25a3bc9d6@gmail.com> (raw)
In-Reply-To: <11177953.afHAXk0WbW@omega>
On 2020-12-28 2:08 p.m., Bruno Haible wrote:
> Ron Eggler wrote:
>> 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 */
> Ron,
>
> Please don't waste Paul's time. You got the answer already:
>
> https://lists.gnu.org/archive/html/bug-gnulib/2020-12/msg00197.html
My apologies, I didn't mean to waste anyone's time! As for your answer,
I have downloaded, extracted & copied the new directory (m4-2020-12-26/)
parallel to the existing m4-native/ directory but have not been able to
update the paths correctly yet.
next prev parent reply other threads:[~2020-12-29 2:33 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
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 [this message]
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=6072c1ba-eddf-5fcf-676c-3ce25a3bc9d6@gmail.com \
--to=ron.eggler@gmail.com \
--cc=bruno@clisp.org \
--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).