Re: [Caml-list] use cc instead of gcc as default C compiler?

[Adrien Nader <adrien@notk.org>]

On Mon, Oct 23, 2017, Christopher Zimmermann wrote:
> 
> 
> On October 23, 2017 9:57:07 AM CEST, Gabriel Scherer <gabriel.scherer@gmail.com> 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