On Thu, May 15, 2008 at 8:40 AM, Stefano Zacchiroli <zack@upsilon.cc> wrote:
> On Thu, May 15, 2008 at 01:27:19PM +0100, Richard Jones wrote:
>  > ... but yes we found a build problem on PPC & PPC64.  It looks very
>  > simple to fix actually, but if you did want to take a look then here's
>  > the build log:
>  >
>  > http://koji.fedoraproject.org/koji/getfile?taskID=605617&name=build.log (ppc)
>
>  Curiously enough this didn't show up in Debian. Is it related to gcc in
>  use? Debian buildd is here:
>
>   http://buildd.debian.org/fetch.cgi?pkg=bin-prot;ver=1.0.5-4;arch=powerpc;stamp=1210555306
>
>  and was using gcc 4.3.0.

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!

Regards,
Markus

-- 
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com