On Wed, 2 Dec 2009, Cyril Brulebois wrote:
Firstly, strerror() is not
required to be reentrant by SUSv2 [0], which is the one and only
standard that lbzip2 is coded against. Secondly, incredible it might
seem, I even know about strerror_r(), and if you grep the source for
it, you'll find that I
Hi.
Wrt. to the compilation error itself: this is a standards-non-compliance
bug in GNU/kFreeBSD; SUSv2 mandates those STREAMS related error numbers
[2] [3]. I'm not saying GNU/kFreeBSD should support STREAMS, but it
should #define those macros. (Or maybe GNU/kFreeBSD doesn't even intend
to
On Thu, 3 Dec 2009, Petr Salinger wrote:
We try to support SUSv3, but not all optional parts,
the streams related errors are marked as OB XSR by POSIX 2008.
Note that POSIX 2008 is SUSv4, not SUSv3. In my understanding,
XPG4v2 - Issue 4, Version 2 - SUSv1 - UNIX 95
XPG5(?) - Issue 5
Package: lbzip2
Version: 0.18-2
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS on GNU/kFreeBSD:
| gcc $(/bin/sh lfs.sh CFLAGS) -D _XOPEN_SOURCE=500 -pipe -ansi -pedantic -g3
-Wall -O2 -c main.c
| main.c:115: error: 'ENODATA'
On Tue, 1 Dec 2009, Cyril Brulebois wrote:
your package FTBFS on GNU/kFreeBSD:
| gcc $(/bin/sh lfs.sh CFLAGS) -D _XOPEN_SOURCE=500 -pipe -ansi -pedantic -g3
-Wall -O2 -c main.c
| main.c:115: error: 'ENODATA' undeclared here (not in a function)
| main.c:125: error: 'ENOSR' undeclared here (not
Hi.
ERSEK Laszlo la...@caesar.elte.hu (01/12/2009):
Oh thank you for your kind words. Firstly, strerror() is not
required to be reentrant by SUSv2 [0], which is the one and only
standard that lbzip2 is coded against. Secondly, incredible it might
seem, I even know about strerror_r(), and if
6 matches
Mail list logo
