From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.4 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id A9839BBAF for ; Thu, 15 May 2008 17:59:04 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AusFAHb6K0hA6aq7d2dsb2JhbACDHY8EAQwFAgQJDwWVCYYQ X-IronPort-AV: E=Sophos;i="4.27,492,1204498800"; d="scan'208";a="26216175" Received: from discorde.inria.fr ([192.93.2.38]) by mail4-smtp-sop.national.inria.fr with ESMTP; 15 May 2008 17:59:04 +0200 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m4FFx3En001873 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Thu, 15 May 2008 17:59:04 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AusFAHb6K0hA6aq7d2dsb2JhbACDHY8EAQwFAgQJDwWVCYYQ X-IronPort-AV: E=Sophos;i="4.27,492,1204498800"; d="scan'208";a="26216174" Received: from rn-out-0910.google.com ([64.233.170.187]) by mail4-smtp-sop.national.inria.fr with ESMTP; 15 May 2008 17:59:03 +0200 Received: by rn-out-0910.google.com with SMTP id i6so166140rng.2 for ; Thu, 15 May 2008 08:59:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=tl+R/rXpc+LttViYruYRCEagYu3P15X9pFNfdx7l2s0=; b=TevZ18b36RQ54/L3FUBLL7EUtXLW7qb98khm29hHRGbU8GtEaKmILtAAf/VlqbaDgpSQj0zB8eQOWjDmx3g5pNt2ZVGhA58vbZZ/lIxpgNi3iakwZJQ0Dz9JN32dDTSmxPdf/NTH7hyaq+XaAGWmSBIfdl5riTqHVShfcGrI+zY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DtCqU6FO+eUSLXLAQUCoTfTjcw1M+r7hhrQ+Om8oE8mToRlrWF+v/ERkkl162rcCLrwQRIN9jROqETlJazSfLwOuvEoEn1kMv06Z737RwWOaD7o9LN1vEpQ+w0mi4y0yHFujsmmaPmcBVKH8bAOn1IuUs4ndWN17IXErXNDduts= Received: by 10.142.72.21 with SMTP id u21mr1061832wfa.65.1210867141310; Thu, 15 May 2008 08:59:01 -0700 (PDT) Received: by 10.143.17.15 with HTTP; Thu, 15 May 2008 08:59:00 -0700 (PDT) Message-ID: Date: Thu, 15 May 2008 11:59:00 -0400 From: "Markus Mottl" To: "Caml List" Subject: Re: [Caml-list] Core has landed In-Reply-To: <20080515124023.GA4797@aquarium.takhisis.invalid> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1209764381.8680.38.camel@nyc-qws-018.delacy.com> <20080503081946.GA30935@annexia.org> <891bd3390805030356n1988a6cep5f7d4263ae30cffe@mail.gmail.com> <20080515122719.GA2842@annexia.org> <20080515124023.GA4797@aquarium.takhisis.invalid> X-Miltered: at discorde with ID 482C5DC7.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; markus:01 mottl:01 markus:01 mottl:01 zacchiroli:01 zack:01 0100,:01 gcc:01 buildd:01 buildd:01 powerpc:01 gcc:01 compilation:01 compilation:01 ocaml:01 On Thu, May 15, 2008 at 8:40 AM, Stefano Zacchiroli 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