ISTR years ago seeing some C magic, where in a compile time declaration, one packs bytes into a struct union with an integer, and then at runtime looks at the integer value to determine the endianess on the fly. Downside: it has to be tested at runtime, which means the compile time optimizer is less likely to remove the unused code paths.
Is it the case that the C standard or the POSIX standard do not define a standard #define that tells the current endianess? That seems like just the sort of thing that the standard should do... ..m On Tue, May 23, 2017 at 11:59 AM Hal Murray <hmur...@megapathdsl.net> wrote: > If you are keeping track... > > It builds and runs on a 32 bit PowerPC MAC-Mini, both Debian and FreeBSD. > > #define WORDS_BIGENDIAN 1 > > There are problems with the firmware setting up the time keeping parameters > incorrectly. I can patch it via Open Firmware, but haven't figured out how > to make it stick over reboots. > > > -- > These are my opinions. I hate spam. > > > > -- Mark Atwood http://about.me/markatwood +1-206-604-2198 SMS & Signal
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
