Re: build problems on old Linux libc5

2008-04-19 Thread Bruno Haible
Alain Guibert wrote: > > The behaviour change in "checking for long long int" is intended. The > > users of the gnulib macros now expect to be able to use long longs in > > preprocessor directives (even if there are some known bugs with values > > outside the 32-bit 'int' range). > > But the prepr

anything pending? coreutils-6.11 imminent

2008-04-19 Thread Jim Meyering
Hello, I'm about to release coreutils-6.11, so this may really be the final call. If you have changes for gnulib or coreutils that you think should be in a stable release, please let me know ASAP (like within an hour or two). Currently, I'm planning to use gnulib v0.0-513-g2e89567, which has unde

Re: output rounding bug in vasnprintf %e format implementation

2008-04-19 Thread Ben Pfaff
Bruno Haible <[EMAIL PROTECTED]> writes: > Ben Pfaff wrote: >> [This issue arose in examination of bug 22924 against GNU PSPP, >> which may be viewed at https://savannah.gnu.org/bugs/?22924.] >> >> The %e format implemented by gnulib's vasnprintf (when >> NEED_PRINTF_DOUBLE is defined) does not r

Re: output rounding bug in vasnprintf %e format implementation

2008-04-19 Thread Bruno Haible
Ben Pfaff wrote: > By adding a printf > around here, I can see that floorlog10 chooses an exponent of 3. The floorlog10 function was intended to return a result with at most 10^-7 error. There was a bug here too (I confused log and log2.) This fixes it. 2008-04-19 Bruno Haible <[EMAIL PROTECTE

Re: output rounding bug in vasnprintf %e format implementation

2008-04-19 Thread Bruno Haible
Ben Pfaff wrote: > [This issue arose in examination of bug 22924 against GNU PSPP, > which may be viewed at https://savannah.gnu.org/bugs/?22924.] > > The %e format implemented by gnulib's vasnprintf (when > NEED_PRINTF_DOUBLE is defined) does not round properly in all > cases. Here is one exampl

updated [Re: new snapshot, and a huge set of coreutils test results

2008-04-19 Thread Jim Meyering
Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> I'm publishing this mainly so that people who care about the affected >> platforms can investigate further. > > As a first step to that: the list of failing tests: > > $ grep '^FAIL:' * | sort -k2 > go.2008.04.14.07.01.55.log:FAIL: 2g