Akshay Adiga <akshay.ad...@linux.vnet.ibm.com> writes: > An application built using glibc would expect __BYTE_ORDER to tell if > it should be compiled for BIG_ENDIAN or LITTLE_ENDIAN, whereas ccan uses > HAVE_LITTLE_ENDIAN and HAVE_BIG_ENDIAN for the same purpose. > > Hence setting __BYTE_ORDER based on what CCAN provides will no longer > break the applications which check endianness the glibc way.
Thanks, applied! Cheers, Rusty. _______________________________________________ ccan mailing list ccan@lists.ozlabs.org https://lists.ozlabs.org/listinfo/ccan
