Googling found this exchange:
# sandhu <sandesh....@xxxxxxxxx> wrote:
# > I have included fcntl and stat and types.h
# > but still it showing undefined O_BINARY...............
#
# Because it's an undefined constant. For hopefully the last time:
#
# UNDER UNIX THERE IS NO DIFFERENCE BETWEEN TEXT AND BINARY FILES.
#
# None, nada, zilch - they are just sequences of bytes. And because
# of this there is absolutely no reason at all to define a constant
# named O_BINARY or make it a flag that gets accepted by open().
If the exact same source code will run on Microcrap and Unix
once O_BINARY is defined to 0 for Unix, then there is very
good reason to use it.
So I added
# define O_BINARY 0
and everything seems fine.
----- Original Message -----
From: "Louis P Zulli" <[email protected]>
To: [email protected]
Sent: Tuesday, December 30, 2008 3:25:15 PM GMT -05:00 US/Canada Eastern
Subject: [Bug-gnubg] gnubg compile failure
Hi,
I attempted to compile the latest snapshot. Ran into
util.c: In function ‘TEMP_g_mkstemp’:
util.c:130: error: ‘O_BINARY’ undeclared (first use in this function)
util.c:130: error: (Each undeclared identifier is reported only once
util.c:130: error: for each function it appears in.)
make[2]: *** [util.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Any thoughts?
Thanks,
Louis
_______________________________________________ Bug-gnubg mailing list
[email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg
