From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zhi.han@gmail.com>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 573F97EE25
	for <caml-list@sympa.inria.fr>; Tue,  5 Nov 2013 17:14:12 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  zhi.han@gmail.com) identity=pra; client-ip=209.85.192.181;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="zhi.han@gmail.com";
  x-sender="zhi.han@gmail.com"; x-conformance=sidf_compatible
Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of
  zhi.han@gmail.com designates 209.85.192.181 as permitted
  sender) identity=mailfrom; client-ip=209.85.192.181;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="zhi.han@gmail.com";
  x-sender="zhi.han@gmail.com"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@mail-pd0-f181.google.com) identity=helo;
  client-ip=209.85.192.181;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="zhi.han@gmail.com";
  x-sender="postmaster@mail-pd0-f181.google.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcCAKgYeVLRVcC1m2dsb2JhbABZhBK/Xn0IFg4BAQEBAQYLCwkUKIIcUAEMDx4DEggBB10BEQEFARAGAgKICQEDD50YgwSMV4MJhCwKGScNZIkBAQUMjiGBSYQZA4lAjkqQHRgphG8egS4
X-IPAS-Result: AgcCAKgYeVLRVcC1m2dsb2JhbABZhBK/Xn0IFg4BAQEBAQYLCwkUKIIcUAEMDx4DEggBB10BEQEFARAGAgKICQEDD50YgwSMV4MJhCwKGScNZIkBAQUMjiGBSYQZA4lAjkqQHRgphG8egS4
X-IronPort-AV: E=Sophos;i="4.93,640,1378850400"; 
   d="scan'208";a="33863214"
Received: from mail-pd0-f181.google.com ([209.85.192.181])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 05 Nov 2013 17:14:11 +0100
Received: by mail-pd0-f181.google.com with SMTP id x10so8626422pdj.26
        for <caml-list@inria.fr>; Tue, 05 Nov 2013 08:14:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=vHM/BarPUq+xfmLJO3EJeyr6sRkcFHWWfBg7TWv6Xic=;
        b=x33qXuhcQmdfdN6lMdR3Nk4hpqilxgj2Jdm/fY+jEbz5QXY2tg2V9tywJHeHWLWmH8
         jMvQG2VBGKptIOWoOpFIHE4ndmYrkRrfFTzBZeEq77MezmqRdNDZ8BQP9HguQxHNdmtm
         GBZTNmcblf+o2lZK1NgeXDye+56pU+7H1nu5UH6bNHTHagUCMaspUc/PQb8WqclcPcqm
         /ACPuI2RO1QOIU2wFfv6zqChdK98yxpK9t1iAHaL2HltrkcO7+qqNNAArU+i0gcD4xk9
         Z57lzw49wHWdK1M30YJW5u0XzT/n2Uw6H/3Ih9k35sPwDWL3lHeWMBtz6eDI+KVeKRl9
         xKpg==
MIME-Version: 1.0
X-Received: by 10.68.254.105 with SMTP id ah9mr23919679pbd.87.1383668049268;
 Tue, 05 Nov 2013 08:14:09 -0800 (PST)
Received: by 10.70.15.68 with HTTP; Tue, 5 Nov 2013 08:14:09 -0800 (PST)
Date: Tue, 5 Nov 2013 11:14:09 -0500
Message-ID: <CABUhoU4tjQPaszD8_-oQ=JQgcwhNgg8s=CNXUbNuSU+C7TWBVw@mail.gmail.com>
From: Zhi Han <zhi.han@gmail.com>
To: caml-list@inria.fr
Content-Type: multipart/alternative; boundary=047d7b2e10439059dd04ea7052fb
Subject: [Caml-list] 


--047d7b2e10439059dd04ea7052fb
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am helping managing ocaml in my company. We have encountered difficulties
while upgrading to Debian 7. We are using different versions of gcc. And it
seems that ocaml has written a hard-coded path to gcc while building
itself. And this path is burned in: every time the installed ocaml tries to
compile and link it will use this path.

My question is, is there a way to avoid burning in this path and explicitly
pass the path to gcc while using the compiler?

Thanks for your reply.

---------------
Zhi Han

--047d7b2e10439059dd04ea7052fb
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div><div>Hi,<br><br></div>I am helping managing ocaml in my company. We
 have encountered difficulties while upgrading to Debian 7. We are using
 different versions of gcc. And it seems that ocaml has written a 
hard-coded path to gcc while building itself. And this path is burned 
in: every time the installed ocaml tries to compile and link it will use
 this path. <br>
<br></div>My question is, is there a way to avoid burning in this path and explicitly pass the path to gcc while using the compiler? <br clear="all"><div><br></div><div>Thanks for your reply.<br><br></div>---------------<br>

Zhi Han
</div>

--047d7b2e10439059dd04ea7052fb--