From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 DADF3801D7 for ; Mon, 23 Oct 2017 21:50:26 +0200 (CEST) Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=adrien@notk.org; spf=Pass smtp.mailfrom=adrien@notk.org; spf=None smtp.helo=postmaster@nautica.notk.org Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; 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@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible IronPort-PHdr: =?us-ascii?q?9a23=3AoENzWhS0c/AoVGJNwL5QvjgLYdpsv+yvbD5Q0YIu?= =?us-ascii?q?jvd0So/mwa64ZBeN2/xhgRfzUJnB7Loc0qyN7PCmBDRIyK3CmU5BWaQEbwUCh8?= =?us-ascii?q?QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnY6Uy/yPgtt?= =?us-ascii?q?J+nzBpWaz4Huj7jzqNXvZFBjhCC8eq91NBW7t03jt8wTjJFnI6A3gk/ComFJYP?= =?us-ascii?q?hR3WNlP3qcmhvm4sa2upJupXd+ofUkoudMS6T3eeweRLBVFnxyOmwv5cDtnR/E?= =?us-ascii?q?UQjJ4WETBDZF2iFUChTIuUmpFqz6tTH3468kgHGX?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A/AgDPR+5Z/5NHeVtbGwEBAQMBAQEJA?= =?us-ascii?q?QEBFQEBAQECAQEBAQgBAQEBgzSBUieDeplkgXoSiDmPfwqFOwKEVEIVAQEBAQE?= =?us-ascii?q?BAQEBAQFqKII4BQEeAQWCPAEFIw8BRhALGAICBRMOAgIPBQ0LMROKCAMZqA+CJ?= =?us-ascii?q?4dFDYNTAQEBAQYBAQEBJIEPgh+CB4FQhROCXoU7L4IyBaEqPI97hGwNc5IujQy?= =?us-ascii?q?IcIE5NSKBWzQhCCoISYJkhGE+NopagVUBAQE?= X-IPAS-Result: =?us-ascii?q?A0A/AgDPR+5Z/5NHeVtbGwEBAQMBAQEJAQEBFQEBAQECAQE?= =?us-ascii?q?BAQgBAQEBgzSBUieDeplkgXoSiDmPfwqFOwKEVEIVAQEBAQEBAQEBAQFqKII4B?= =?us-ascii?q?QEeAQWCPAEFIw8BRhALGAICBRMOAgIPBQ0LMROKCAMZqA+CJ4dFDYNTAQEBAQY?= =?us-ascii?q?BAQEBJIEPgh+CB4FQhROCXoU7L4IyBaEqPI97hGwNc5IujQyIcIE5NSKBWzQhC?= =?us-ascii?q?CoISYJkhGE+NopagVUBAQE?= X-IronPort-AV: E=Sophos;i="5.43,424,1503352800"; d="scan'208";a="242072298" Received: from nautica.notk.org ([91.121.71.147]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2017 21:49:55 +0200 Received: by nautica.notk.org (Postfix, from userid 1003) id AD761C009; Mon, 23 Oct 2017 21:49:54 +0200 (CEST) Date: Mon, 23 Oct 2017 21:49:54 +0200 From: Adrien Nader To: Christopher Zimmermann Cc: Gabriel Scherer , caml users Message-ID: <20171023194954.GA13292@notk.org> References: <20171019170538.73d6473c@mortimer.gmerlin.de> <441EA0D0-D075-4407-B50D-8CAEDD6039DF@gmerlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <441EA0D0-D075-4407-B50D-8CAEDD6039DF@gmerlin.de> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] use cc instead of gcc as default C compiler? On Mon, Oct 23, 2017, Christopher Zimmermann wrote: > > > On October 23, 2017 9:57:07 AM CEST, Gabriel Scherer wrote: > >My guess is that cc is a broken compiler on many exotic operating > >system > >(or at least was when the ./configure was first written in the > >nineties), > >and in particular does not support the (modest) gcc extensions that the > >runtime relies on. Using a standardized (yet portable) compiler was > >deemed > >an easier path to configure the OCaml distribution build system than > >trying > >to support the oddities of every Unix's C compiler under the sun. > > > >Note that the compiler distribution builds just fine under MacOS, which > >now > >uses Clang (llvm) instead of GCC -- and that you can configure the C > >compiler you want to use with (./configure -cc ...). I don't see what > >is > >the problem here; and I would think that opting to choose GCC by > >default is > >still a perfectly reasonable choice today. > > > My Problem is that custom OCaml builds, especially the ones done through opam will use gcc and therefore fail to build projects with not so modest requirements. At the moment I'm just wondering at which level in the toolchain this neuds fixing. OCaml configure, opam-repository or opam source? Could you elaborate on that « therefore fail to build projects with not so modest requirements » ? -- Adrien