bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Ron Eggler <ron.eggler@gmail.com>
Subject: Re: port freadahead.c & fseeko.c
Date: Thu, 24 Dec 2020 02:38:35 +0100	[thread overview]
Message-ID: <2841046.YzqhA4RPaI@omega> (raw)
In-Reply-To: <CAHxBh_T5gn6FhzLpxLaVYqt8aLsVM1fhLO8G=0zjL-WkyM_Dyg@mail.gmail.com>

Ron Eggler wrote:
> 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."
>       |   ^~~~~

You didn't say which operating system you have on your "DIGI UL6 SBC".

Therefore I'd recommend to try the newest m4 tarball, from
  https://gitlab.com/gnu-m4/ci-distcheck/-/jobs/artifacts/master/raw/m4-snapshot.tar?job=check-optimized
instead of m4-1.4.17. This tarball supports more operating systems than
the one of m4-1.4.17 (because it uses the newest gnulib).

Bruno



  parent reply	other threads:[~2020-12-24  1:38 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
2020-12-29  3:48         ` Bruno Haible
2020-12-24  1:38 ` Bruno Haible [this message]
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=2841046.YzqhA4RPaI@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=ron.eggler@gmail.com \
    /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).