Hi Niko, and thanks for the quick follow-up. Niko Tyni <firstname.lastname@example.org> (20/05/2012): > See the attached patch, which just makes 'len' an int and removes the > problematic pointer cast. I wonder if the STRLEN cast on becomes an > issue, though. Is it possible that an int doesn't fit into a size_t > variable somewhere? If you were asking for a test-build, the answer is: no more FTBFS on s390x. On the int/size_t thingy, quoting : | ISO/IEC 9899:1990, Programming Languages - C (ISO C) left the definition | of the short int, the int, the long int, and the pointer deliberately | vague to avoid artificially constraining hardware architectures that | might benefit from defining these data types independent from the other. | The only constraints were that ints must be no smaller than shorts, and | longs must be no smaller than ints, and size_t must represent the | largest unsigned type supported by an implementation. It is possible, | for instance, to define a short as 16 bits, an int as 32 bits, a long as | 64 bits and a pointer as 128 bits. The relationship between the | fundamental data types can be expressed as: | | sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long) = sizeof(size_t) 1. http://www.unix.org/whitepapers/64bit.html Thanks for your time. Mraw, KiBi.
Description: Digital signature