From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: _FILE_OFFSET_BITS problem on Solaris 10 due to new stdbool.h handling
Date: Sun, 22 Jan 2023 11:39:19 +0100 [thread overview]
Message-ID: <6046887.FrDkFHEb2X@nimes> (raw)
In-Reply-To: <65ea1fb5-d901-1431-2a7c-aecff76cc93d@cs.ucla.edu>
Paul Eggert wrote:
> I ran into a problem on Solaris 10 gcc
Thanks. I reproduce it on Solaris 10, 32-bit mode, with cc but not with gcc:
cc -D_STDC_C99= -O -DHAVE_CONFIG_H -I. -I../../gllib -I.. -DGNULIB_STRICT_CHECKING=1 -I/home/haible/prefix-x86/include -D_REENTRANT -g -c -o stackvma.o ../../gllib/stackvma.c
"/usr/include/stdio.h", line 321: syntax error before or at: off_t
In GNU libsigsegv, there is nothing to do because libsigsegv does not set
_FILE_OFFSET_BITS=64. But for 'grep', evidently, it is important to be able
to access files larger than 2 GB.
I propagated the fix to the two stable branches.
Bruno
next prev parent reply other threads:[~2023-01-22 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 6:57 _FILE_OFFSET_BITS problem on Solaris 10 due to new stdbool.h handling Paul Eggert
2023-01-22 10:39 ` Bruno Haible [this message]
2023-01-22 20:56 ` Paul Eggert
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=6046887.FrDkFHEb2X@nimes \
--to=bruno@clisp.org \
--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).