[STATUS] (apr) Wed Nov 5 23:45:25 EST 2003

2003-11-06 Thread Rodent of Unusual Size
APACHE PORTABLE RUNTIME (APR) LIBRARY STATUS: -*-text-*- Last modified at [$Date: 2003/06/26 18:17:44 $] Release: 0.9.3 : tagged March 30, 2003 0.9.2 : released March 22, 2003 0.9.1 : released September 11, 2002 0.9.0 : released August 28, 2002

[STATUS] (apr-util) Wed Nov 5 23:45:37 EST 2003

2003-11-06 Thread Rodent of Unusual Size
APRUTIL LIBRARY STATUS: -*-text-*- Last modified at [$Date: 2003/03/31 05:32:43 $] Release: 0.9.3 : Tagged March 30, 2002 0.9.2 : Released March 22, 2002 (alpha) 0.9.1 : Released September 11, 2002 (alpha) 0.9.0 : Not released

Re: cvs commit: apr configure.in

2003-11-06 Thread Ben Laurie
[EMAIL PROTECTED] wrote: jorton 2003/11/06 01:18:22 Modified:.configure.in Log: * configure.in: Fix endianness detection with autoconf 2.1x. Speaking of autoconf, I get this every time: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot' WARNING: and

Re: cvs commit: apr/random/unix apr_random.c

2003-11-06 Thread Joe Orton
On Wed, Nov 05, 2003 at 11:32:07PM +, Ben Laurie wrote: Branko ibej wrote: Ben Laurie wrote: Jeff Trawick wrote: /* FIXME: this is not C99 or C++ or Java */ What's the matter? Did your editor break? :-) Besides, your revision is wrong... /* FIXME:

Re: cvs commit: apr configure.in

2003-11-06 Thread Aaron Bannert
What is this and the APR_IS_BIGENDIAN macro used for? Do we have any code that is endian-dependent? -aaron On Thu, Nov 06, 2003 at 09:18:23AM -, [EMAIL PROTECTED] wrote: jorton 2003/11/06 01:18:22 Modified:.configure.in Log: * configure.in: Fix endianness

Re: cvs commit: apr configure.in

2003-11-06 Thread Joe Orton
On Thu, Nov 06, 2003 at 08:27:57AM -0800, Aaron Bannert wrote: What is this and the APR_IS_BIGENDIAN macro used for? Do we have any code that is endian-dependent? $ grep -l -r --include \*.c APR_IS_BIGENDIAN . ./random/unix/sha2.c On Thu, Nov 06, 2003 at 09:18:23AM -, [EMAIL PROTECTED]

Re: cvs commit: apr configure.in

2003-11-06 Thread Aaron Bannert
On Nov 6, 2003, at 8:55 AM, Joe Orton wrote: On Thu, Nov 06, 2003 at 08:27:57AM -0800, Aaron Bannert wrote: What is this and the APR_IS_BIGENDIAN macro used for? Do we have any code that is endian-dependent? $ grep -l -r --include \*.c APR_IS_BIGENDIAN . ./random/unix/sha2.c Ah, I didn't pick up

Re: cvs commit: apr/random/unix apr_random.c

2003-11-06 Thread Ben Laurie
[EMAIL PROTECTED] wrote: trawick 2003/11/06 08:26:09 Modified:random/unix apr_random.c Log: fix an odd portability issue: Bit-field foo must be of type signed int, unsigned int or int. Thanks. BTW, on the subject of bitfield gotchas, never make boolean fields signed -

Re: cvs commit: apr/random/unix apr_random.c

2003-11-06 Thread Jeff Trawick
Ben Laurie wrote: BTW, on the subject of bitfield gotchas, never make boolean fields signed - why? Coz: struct x { signed int onebitfield:1; } x; signed int someint; x.onebitfield=TRUE; someint=TRUE; assert(x.onebitfield == someint); /* SPLAT!!! */ :)

Re: uuid generation on linux boxes

2003-11-06 Thread C. Michael Pilato
Ian Holsman [EMAIL PROTECTED] writes: I have a issue with a linux box not having enough entropy and hanging on a call to apr_uuid_get (as it calls /dev/random) I was wondering why we don't just use /proc/sys/kernel/random/uuid and use that for our uuid? If you are building APR yourself, I