On Thu, May 15, 2008 at 11:59 AM, Markus Mottl <[EMAIL PROTECTED]> wrote: > It seems that this is related to the PPC architecture defaulting to > unsigned as opposed to signed chars. I don't know what the best fix > for this is. Maybe gcc 4.3.0 changes this default behavior. I guess > that using the compilation flag "-no-unsigned-char" might fix this in > the general case. Could anybody with access to a PPC platform please > verify, whether this flag solved this compilation problem for the > binary protocol library? Thanks!
Oops, typo. The compilation flag in question is called "-fno-unsigned-char". Regards, Markus -- Markus Mottl http://www.ocaml.info [EMAIL PROTECTED] _______________________________________________ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
