[PATCH] Fix parsing of empty variable settings on the command line.

2010-07-19 Thread Ralf Wildenhues
* lib/autoconf/general.m4 (_AC_INIT_PARSE_ARGS): Work around expr bug returning 0 instead of the empty string. * lib/autotest/general.m4 (AT_INIT): Likewise. Signed-off-by: Ralf Wildenhues --- * Ralf Wildenhues wrote on Tue, Jul 20, 2010 at 07:09:03AM CEST: > I don't get it, esp. I don't get why

AT_ARG_OPTION_ARG test failure

2010-07-19 Thread Ralf Wildenhues
I don't get it, esp. I don't get why I haven't seen this anywhere before. This is with bash 3.2.39 on Debian GNU/Linux x86. Can anyone confirm this failure? Otherwise I guess I should go looking for weird stuff in my setup. Anyway, rerunning ./micro-suite -x 1 FROB=default FROB_ARG= in the t

RE: how to detect int64?

2010-07-19 Thread Jay K
> This algorithm doesn't work on machines with padding bits, > that is, unused bits in the representation. It's possible, for example > for CHAR_BIT to be 8, sizeof (unsigned int) to be 4, but UINT_MAX > is 2**31 - 1 (not 2**62 - 1), because the hardware simply doesn't support > unsigned arit

Re: how to detect int64?

2010-07-19 Thread Eric Blake
On 07/19/2010 03:30 PM, Jay K wrote: > >> Which version of autoconf generated the configure that produced the >> output you are questioning? > > It is xz-4.999.9beta.tar.gz from http://tukaani.org/xz/. > I was using gcc 4.2, but now 4.3 and I haven't retried with 4.3.5 yet. > > > configure says

RE: how to detect int64?

2010-07-19 Thread Jay K
> Which version of autoconf generated the configure that produced the > output you are questioning? It is xz-4.999.9beta.tar.gz from http://tukaani.org/xz/. I was using gcc 4.2, but now 4.3 and I haven't retried with 4.3.5 yet. configure says: # Generated by GNU Autoconf 2.64 for XZ Utils 4.999

Re: Need your help

2010-07-19 Thread Eric Blake
[Reading through my mail backlog, I found this thread was unanswered] On 07/06/2010 12:08 AM, raj.abhis...@gmail.com wrote: > [Nothing?] If you still need help, please supply more details; and a more descriptive subject line would be helpful, too. Make sure you send a plaintext email; perhaps

Re: how to detect int64?

2010-07-19 Thread Paul Eggert
On 07/18/10 19:01, Jay K wrote: > So, question is, what is wrong with the following seems-simple algorithms: > > > 1) Find the types that exist, char, short, int, long, long long, > their sizes, #include , multiply by CHAR_BIT? > Or probably assume all but long long exist. > Or error out i

Re: how to detect int64?

2010-07-19 Thread Eric Blake
On 07/18/2010 08:01 PM, Jay K wrote: > > scary configure output noticed: > > checking for int64_t... int > checking for uint64_t... unsigned int > > config.h: > /* Define to the type of a signed integer type of width exactly 64 bits if >such a type exists and the standard includes do not def

how to detect int64?

2010-07-19 Thread Jay K
scary configure output noticed: checking for int64_t... int checking for uint64_t... unsigned int config.h: /* Define to the type of a signed integer type of width exactly 64 bits if    such a type exists and the standard includes do not define it. */ #define int64_t int Looks like a known/fixe