Re: [bug-recutils] [Platform-testers] recutils pre-release 1.4.91 in alpha.gnu.org

[Jose E. Marchesi]

Hi Bruno!
    
    * Linux/PowerPC (both 32-bit and 64-bit)
    * Linux/SPARC (64-bit)
    * MacOS X 10.5 (both 32-bit and 64-bit)
    * NetBSD 5.1
    * OpenBSD 4.9
    * Cygwin 1.7.9
    
      recsel-confidential fail (see recsel-confidential.diff)
      recsel-confidential-fex fail (see recsel-confidential-fex.diff)
      recsel-confidential-fex-value fail (see 
recsel-confidential-fex-value.diff)
      recsel-confidential-num fail (see recsel-confidential-num.diff)
    FAIL: recsel.sh
    
    Find the files attached.

It looks like in those systems libgcrypt is not available, so the output
of the tests contains the encrypted strings.  I must put in place
something in the tests to recognize such cases to not run the encryption
related stuff.

    
------------------------------------------------------------------------------
    
    * AIX 5.3
    * Solaris 9, 10
    * mingw
    
    [...]
    ld: 0711-317 ERROR: Undefined symbol: .strcasestr

    * IRIX 6.5
    
    Btw, what is the encoding of the strings on which rec-record.c uses
    strcasestr() and strstr()? If it can be a multi-byte encoding other than
    UTF-8 (such as BIG5 or GB18030), the functions strstr() and strcasestr()
    can produce wrong matches. If you know the encoding is the locale encoding
    (depends on $LANG), then you should better use the gnulib modules
    'mbsstr' and 'mbscasestr' instead. If, however, you don't know the encoding
    at all, then forget about this functionality, and don't use strstr() nor
    strcasestr().

I imported the strcasestr module from gnulib.  The recfiles are supposed
to contain UTF-8 strings.
    
    * HP-UX 11.00
    * OSF/1 5.1
    
      recinf-one-record fail (see recinf-one-record.diff)
      recinf-multiple-records fail (see recinf-multiple-records.diff)
      recinf-multiple-named fail (see recinf-multiple-named.diff)
      recinf-multiple-types fail (see recinf-multiple-types.diff)

Those ones are due because in those systems %zd does not work in printf
strings.  I am using %zd in order to avoid a warning in recent versions
of gcc regarding printf and size_t.  Do you know about a portable and
safe format string to print size_t values?

Thanks for the report!
    
-- 
Jose E. Marchesi         http://www.jemarch.net
GNU Project              http://www.gnu.org