Without the actual config.log it's hard to tell what's going on. You may send it to me privately if you want.
If you have a working <endian.h> or <mach/endian.h>, we shouldn't need to run a test program. but i have never written an iphone app, so i have really no idea if they have such a header. If they don't have any tests that don't require running a program, i could probably add a hack to allow the user to force it, or to disable the little-endian optimizations (which turns the code portable). - dave On Mar 3, 11:33 am, marc <vaill...@cis.jhu.edu> wrote: > On Mar 3, 1:42 pm, Kenton Varda <ken...@google.com> wrote: > > > Sorry, our implementation was designed for servers where binary footprint is > > not a big deal. Maybe try using protobuf-c? > > Ok thanks. Getting the following configure error. Any workaround? > > checking for little-endianness via runtime check... configure: error: > cannot run test program while cross compiling > See `config.log' for more details. > > Marc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
