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=2.8 required=5.0 tests=DNS_FROM_RFC_POST,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id A31CFBBAF for ; Mon, 20 Jul 2009 16:06:38 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AukCACAXZErRVdvSkWdsb2JhbACZHD8BAQEBCQkMBxGlfoEbjiYBAwIEhAgFgT8 X-IronPort-AV: E=Sophos;i="4.43,234,1246831200"; d="scan'208";a="31430101" Received: from mail-ew0-f210.google.com ([209.85.219.210]) by mail3-smtp-sop.national.inria.fr with ESMTP; 20 Jul 2009 16:06:06 +0200 Received: by ewy6 with SMTP id 6so2268201ewy.27 for ; Mon, 20 Jul 2009 07:06:05 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=f28cj9pZbfkWFGnEfEMIxtsQmXqwpxMfLmK8mDP+JaA=; b=rvD3akbWL7DYYQG/FaYjjurdnQFGPecNQtrEOKkaoTAhzYFr+Ex6nMl/+ls46eEyCS LU6i1Qhtvn6I0ldvi3z5Rtvlcm750qA6ldzxxrxW7iB8Pr5KsvbwLzFm5fyKmpuYlrRx +pbSOSbfVPBRrR/9bGX0ONT+ouXcIIG0mxmGo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=hk3YJ3HnaR8fKvNJFW/F7JhxpU9V4CgqtWo0Ku8akQDHZOiv5/CjHrln/P5iZCmCPW B9vAX8vJlEQr3cwBNmL1xVLJcluJoEh32vOMUke15MS7fZvjKlTS6o/OFUsL+T1FQWGU yZFGDYGxdPxczv7zK4HPQRAFvO60coDofffz4= Received: by 10.211.201.8 with SMTP id d8mr3696503ebq.50.1248098765018; Mon, 20 Jul 2009 07:06:05 -0700 (PDT) Received: from ?192.168.0.50? (robertlan.eu.org [81.57.34.8]) by mx.google.com with ESMTPS id 23sm8688053eya.30.2009.07.20.07.06.03 (version=SSLv3 cipher=RC4-MD5); Mon, 20 Jul 2009 07:06:04 -0700 (PDT) Message-ID: <4A6479CB.7080702@gmail.com> Date: Mon, 20 Jul 2009 16:06:03 +0200 From: Alexis ROBERT User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: philippe esperet Cc: caml-list@yquem.inria.fr, francois.boisson@prepas.org Subject: Re: [Caml-list] Caml Light 0.8 and -fstrict-aliasing build issue References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam: no; 0.00; prepas:01 prepas:01 ocaml:01 mpsi:01 ocaml:01 untar:01 gcc:01 gcc:01 makefile:01 0.8:98 2009:98 0.80:98 0.80:98 ubuntu:98 ubuntu:98 philippe esperet a écrit : > francois.boisson@prepas.org > %%%%%%%%%%%%%%%%%%%%% > /dosc/esperet/tex/email/@ocaml9.tex lun. juil. 20 2009 15:01:49 > > % As the MPSI programme force us to use Caml Light instead of OCaml (our > % teachers hit us each time we pronounce ocaml :) ), I tried to build > % the sources on my computer, but during the build, I got this : > > We use Ocaml in henri IV for three years, nevertheless I try for fun > to keep the old camllight each time I change my linux config. At home, > on a 64 bits platform: > > camllight_0.80_amd64.deb from the guru François Boisson > makes the trick with something like (suse 11.1) > > dpkg-deb -x camllight_0.80_amd64.deb / At Fenelon, my teachers tell us they don't want us to have problems with examiners who are not familiar with OCaml, but we can use it if we want, even if everything is under Caml Light there. Thanks for the trick, I was used to manually uncompress it with ar x and then untar data.tar.gz in / :) I've looked into the strings of the binaries bundled in the package and it shows "GCC: (GNU) 3.4.6 (Ubuntu 3.4.6-8ubuntu2)", and -fstrict-aliasing seems disabled in GCC 3.4. The strange thing is that even if gcc-3.4 is in build-dep of the dpkg-source package, I don't see where it uses it in debian/rules or any Makefile (and debuild fails at building the package, it doesn't execute the build step of rules for a reason I don't understand, but if I manually launch the step, I get the same error). Thanks Alexis