Bertrand Bellenot
Bertrand Bellenot
Here is what I got: ``` C:\Users\bellenot>AppData\Local\Continuum\miniconda3\condabin\conda install cling -c conda-forge Collecting package metadata (current_repodata.json): done Solving environment: done ==> WARNING: A newer version of conda exists. conda-forge::ca-certificates-2019.11.28-hecc5488_0 certifi pkgs/main::certifi-2019.9.11-py37_0...
OK, thanks. I never tried to build with ninja... I will try when I have some time
> > OK, thanks. I never tried to build with ninja... I will try when I have some time > > Do you think ninja may be the culprit? I...
> I'm also affected by the `std::endl` / `auto ct = new std::ctype` bug. I built using: > * VS 2019 Release (VS 2015 build tools and CMake generator, Windows...
> @bellenot what is weird is that the cling conda package works for you while it produces that error for us and on our CI. > > I am curious...
@jbsolomon don't worry, as I said, I'll set-up a new virtual machine, we'll see how it goes (but I will need time...)
> Man, I wish cling worked on Windows. It does
You have to build it from source. See the [Cling Build Instructions](https://root.cern/cling/cling_build_instructions/). On Windows, in a `x64 Native Tools Command Prompt for VS 2022`: ``` git clone http://root.cern/git/llvm.git src cd...
@Welding-Torch I'll check what can be done. BTW, is Cling working without Visual Studio installed on the system? I thought the headers were needed... But I'll check nevertheless
Well, AFAIK, Cling (the JIT) needs the header files, as any other compiler