cling goes public!

Submitted by axel on Tue, 30/08/2011 - 21:08

Hi,

We, the cling team, have announced cling, our C++ interpreter prototype! (note: its SVN repository has changed compared with the announcement email; see the build instructions)

To a large extend thanks to Vassil's impressive commitment, cling now behaves like a good C++ interpreter: it runs C++ code that's entered, and prints the results.

[cling]$ #include <cmath>
[cling]$ double x = std::sin(3.1)
(double) 4.158066e-02
[cling]$ .L libz
[cling]$ #include "zlib.h"
[cling]$ zlibVersion()
(const char * const) "1.2.3.4"
$ echo 'extern "C" const char* zlibVersion();
 zlibVersion()' | cling -lz
 
(const char * const) "1.2.3.4"

We have of course already added a few features that we liked from CINT - but cling is a completely new development, based on clang and llvm, a set of compiler libraries (to simplify the matter a bit :-) Vassil will present the innards of cling probably in October; I will post the slides here.

So what's special about cling? It's based on a production-grade compiler and it's designed taking decades of experience with CINT into account. And it doesn't need dictionaries! (Disclaimer: that does not mean that ROOT can do without, automatically. But that's our goal, of course.)

The next steps will be the ones most relevant for High Energy Physics: integration into ROOT (Paul is already working on that) and reloading of changed code (.x myCode.C, edit, .x myCode.C). That latter part is horrible for a compiler.

If you want to check cling out you can simply compile it yourself - it's really easy. I'd love to have an interactive, web-based interface once, but an online C++ interpreter is an invitation for script kiddies to hack the server :-( If you have an idea how to do it please let me know!

Cheers,
Axel

Safety idea

Submitted by KrzaQ (not verified) on Tue, 15/01/2013 - 23:16.
There is a similar project called geordi-prime, it's a haskell-based c++ eval irc bot. The only difference is that it cannot keep state. Anyway, it's publicly available on freenode irc (and countless copies are available elsewhere) and it seems its safety measures are more than enough for irc wannabe hackers. The web-based cling could use the same idea to make sure its safe.

The webpage of geordi-prime: http://www.eelis.net/geordi/

Cling is really great !!! I

Submitted by Devid (not verified) on Mon, 15/10/2012 - 14:04.
Cling is really great !!!

I was able to integrate it in my System on Windows and not I can use C++11 interactively.


Unfortunately there are still some problems with it.
If I try to do following:

#include "my_header.h"


and header includes some other headers that Cling can not find then it will
CRASH in ASTNodeEraser.cpp .

Re: cling on Windows

Submitted by axel on Tue, 16/10/2012 - 02:01.

Hi Devid,

Thanks for trying it out! As we said quite a few times already: cling is not supported on Windows yet. I'm surprised it even starts up. Sorry. This is only going to change next year. We do welcome patches even before, though!

Cheers, Axel

Problem interpreting a function

Submitted by Anonymous (not verified) on Mon, 13/08/2012 - 19:06.
Hello, I've successfully compiled Cling on Mac OSX and seems to work for simple C++ expressions. However when I try to create a C++ function I have a strange error: 
[cling]$ void ff() {
[cling]$ ?   int mm;
[cling]$ ?   mm = 5;
[cling]$ ?   }
input_line_4:2:11: error: expected ';' at end of declaration
 void ff() {
          ^
          ;
[cling]$
This is expected behaviour or am I doing something wrong ?

Use .rawInput

Submitted by vvassilev on Wed, 29/08/2012 - 15:28.
Hi,

The preparseing doesn't work yet and defining a function should happen with the meta command: 

[cling]$.rawInput
[cling]! void ff() {
[cling]! ?   int mm;
[cling]! ?   mm = 5;
[cling]! ?   }
[cling]$.rawInput

Vassil

build time of cling

Submitted by Armin Steinhoff (not verified) on Mon, 06/08/2012 - 18:56.
Hello, The statement "If you want to check cling out you can simply compile it yourself - it's really easy." sounds interesting ... but the time to build cling is extremely high. It takes round about 12h on dual core machine (2.2 Ghz) ! Is there a way to get a binary version for i386 LINUX ? --Armin

Re: Build time

Submitted by axel on Wed, 29/08/2012 - 15:24.

Hi Armin,

No way does it take 12h, something must be terribly wrong with your setup. It should take < 30 minutes even on a laptop. Nevertheless you can pick up a binary version of cling here: https://ecsft.cern.ch/dist/cling Don't be scared by the invalid SSL certificate: it's the best CERN can give to us...

Cheers, Axel

clang/cling for Windows 32/64 - is there any progress ?

Submitted by Vladimir (not verified) on Wed, 09/05/2012 - 10:32.
Is there any progress in supporting Windows 32/64 by clang/cling ? I cannot wait when I could start with cling on Windows platform :-)

Re: Win progress

Submitted by axel on Wed, 29/08/2012 - 15:25.

Hi Vladimir,

Not that I am aware of. We will only get to that next year - unless someone else contributes patches before.

Cheers, Axel.

minor windoze build issue

Submitted by noob men (not verified) on Fri, 04/05/2012 - 00:18.
is the export definition outdated? _ZN4llvm11raw_ostream5writeEPKc* -> _ZN4llvm11raw_ostream5writeEPKcj _ZN4llvm5APInt12initSlowCaseEj* -> _ZN4llvm5APInt12initSlowCaseEjyb _ZTVN4llvm16JITEventListenerE -> _ZN4llvm16JITEventListenerD2Ev _ZN4llvm15SmallVectorBase8grow_podE* -> _ZN4llvm15SmallVectorBase8grow_podEjj dunno about * but gcc refuse that and when build llvm as shared library, cling throw local_cxa_atexit symbol unresolved or something during startup. static library of llvm doesn't cause this

Re: minor windoze build issue

Submitted by axel on Fri, 04/05/2012 - 09:48.

Hi,

Okay, so you are building with GCC on Windows - which one, MingW or cygwin? None of that has ever been tried to my knowledge, and it's unfortunate that the linker doesn't cope with the exports table.

The local_cxa_atexit symbol might not even be needed when building with GCC. Could you open a bug report at https://savannah.cern.ch/bugs/?func=additem&group=savroot? I cannot promise that this will get fixed soon, foryhour configuration, but I would nonetheless like to have a reminder that this issue exists.

For now you are much better off building cling on Linux or MacOS. Take a virtual machine and off you go!

Cheers, Axel

I'm sorry but i'm total noob

Submitted by noob men (not verified) on Mon, 07/05/2012 - 10:21.
I'm sorry but i'm total noob at linux Axel :) I dunno why, everytime i try linux it took less than a day to make me revert to windoze XP :D I use gcc 4.6.3 mingw/msys. you mean that wildcard supposed to resolved by the gcc's linker?

Re: mingw build

Submitted by axel on Wed, 29/08/2012 - 15:27.

Hi,

Sorry - if you cannot get it to work on Windows yourself you're out of luck for now... We will attack cling on Windows only next year.

Cheers, Axel.

Hi Axl, I build latest cling

Submitted by noob men (not verified) on Fri, 04/05/2012 - 00:09.
Hi Axl, I build latest cling for windows, apparently load module .L doesn't work as expected (in the example) [cling]$ .L libz input_line_6:1:10: fatal error: 'libz' file not found #include "libz" Load file failed. I have put zlib.dll zlib.dll.a zlib.a in current folder. Even set LLVM_LIB_SEARCH_PATH doesn't help. More importantly why it treated as #include "libz"? Thank you Axl, cling is great for learning!

Re: libz on Windows

Submitted by axel on Fri, 04/05/2012 - 09:42.

Hi,

"zlib" and "libz" are not the same words :-) Try to rename it to libz.dll, or try .L zlib. And please remember that Windows support is still limited for cling due to clang not fully supporting the Windows C++ API yet.

I'm happy to hear that you like cling, even though you take the rocky Windows road!

Cheers, Axel

This time I tried diagnose it

Submitted by noob men (not verified) on Mon, 07/05/2012 - 10:09.
This time I tried diagnose it with filemon (lowlevel filesystem API monitoring), cling first try exact keyword, then add prefix lib and suffix .a if not found if I use .L libz and cling found static/import library it will complain "Bad image" so I assume it's libz.dll that asked? tried .L zlib.dll and cling found it but throw http://pastebin.com/wZMixLfs

Re: Windows dlopen

Submitted by axel on Wed, 29/08/2012 - 15:28.

Hi,

Sorry, we'll be able to help with the Windows build only next year.

Cheers, Axel.

Syntax Error

Submitted by Anonymous (not verified) on Thu, 03/05/2012 - 04:54.
After I use the make command in the build directory I get this error. I am trying to compile cling. SyntaxError: invalid syntax make[2]: Entering directory `/home/ryan/Documents/build/tools/cling' llvm[2]: Updating Makefile make[2]: Leaving directory `/home/ryan/Documents/build/tools/cling' svn: '/home/ryan/Documents/llvm' is not a working copy File "", line 1 if >= : print "skip" ^ Any help would be appreciated. Thank You.

Re: Syntax Error

Submitted by axel on Fri, 04/05/2012 - 09:37.

Hi,

Can you submit a bug report at https://savannah.cern.ch/bugs/?func=additem&group=savroot, giving the full build log and the output of "svn diff /home/ryan/Documents/llvm"? My suspicion in that you moved / renamed directories after configuring...

Cheers, Axel

clang++

Submitted by Anonymous (not verified) on Tue, 01/05/2012 - 21:45.
I have built clang/llvm but clang++ doesnt seem to work and i think it could potentially be due to the fact that clang++ only works with mac os as far as i know..could i still run cling if clang++ doesnt work...just to clarify clang works perfectly and it compiles my c code flawlessly just clang++ doesnt work. I am using ubuntu 10.04 Thanks!

Actually clang++ works just

Submitted by Misu (not verified) on Mon, 27/08/2012 - 19:19.
Actually clang++ works just fine on Linux, have a look at this article: http://solarianprogrammer.com/2011/10/16/llvm-clang-libc-linux/

Re: clang++

Submitted by axel on Wed, 02/05/2012 - 08:55.

Hi,

Please discuss clang issues at the clang mailing list cfe-dev@cs.uiuc.edu.

Cheers, Axel.

"LastKnownGoodSVNRevision" of cling for ROOT?

Submitted by Constantin (not verified) on Wed, 25/04/2012 - 12:37.
Hello, since i get some errors both during linking (of rootcling_tmp; gives undefined symbol _ZTVN5clang13PragmaHandlerE, though libCling.so is on the path) and compiling (no matching function for call to ‘cling::Interpreter::createUniqueName()’) of ROOT with cling enabled, is it possible to have smth similar to cling's LastKnownGoodLLVMSVNRevision.txt in ROOT?
i.e. some way of telling which revision of Cling does the currently checked-out ROOT revision compile (and link) with?

cheers,
Constantin

Re: cling and ROOT

Submitted by axel on Thu, 26/04/2012 - 13:18.

Hi Constantin!

Thanks for your question. cling is now distributed as part of ROOT, so there cannot be any revision mismatch.

I have updated the build instructions - maybe it's now clearer that one should not build cling next to clang if using ROOT. And I assume that's what's happening in your case, because you seem to have an old libCling used by a new rootcling.

Also, please submit bug reports like this to Savannah, that help's us triaging them properly. Thanks!

Cheers, Axel

osx link issue

Submitted by Anonymous (not verified) on Wed, 21/03/2012 - 16:18.
Any help much appreciated: llvm[4]: Linking Debug+Asserts Shared Library libcling.dylib Undefined symbols: "llvm::APInt::initSlowCase(unsigned int, unsigned long, bool)", referenced from: -exported_symbol[s_list] command line option "cling::Interpreter::executeFile(std::basic_string, std::allocator > const&)", referenced from: -exported_symbol[s_list] command line option

Re: link issue

Submitted by axel on Tue, 27/03/2012 - 17:37.

Hi,

Thanks for your report - should be fixed! But please future report bugs at our bug tracker.

Cheers, Axel.

Thanks for the fix. I'll use

Submitted by Anonymous (not verified) on Tue, 03/04/2012 - 02:35.
Thanks for the fix. I'll use your bug tracker in the future. I wasn't certain that it was a bug and not just something missing on my end. I still get one undefined symbol with latest SVN: "cling::Interpreter::createUniqueName()", referenced from: -exported_symbol[s_list] command line option

Re: bug tracker

Submitted by axel on Wed, 04/04/2012 - 07:42.

Hi,

Thanks for your reports; these things just happen because we still haven't integrated cling into our continuous integration system. I assume it was you who submitted this as a bug on savannah, that's really helpful, thanks a lot!

Cheers, Axel

osx link issue

Submitted by Anonymous (not verified) on Wed, 21/03/2012 - 04:22.
What would cause this after clang builds fine: llvm[4]: Linking Debug+Asserts Shared Library libcling.dylib Undefined symbols: "llvm::APInt::initSlowCase(unsigned int, unsigned long, bool)", referenced from: -exported_symbol[s_list] command line option "cling::Interpreter::executeFile(std::basic_string, std::allocator > const&)", referenced from: -exported_symbol[s_list] command line option "cling::Interpreter::loadFile(std::basic_string, std::allocator > const&, std::basic_string, std::allocator > const*, bool)", referenced from: -exported_symbol[s_list] command line option "cling::MetaProcessor::process(char const*)", referenced from: -exported_symbol[s_list] command line option (maybe you meant: cling::MetaProcessor::process(char const*, cling::Value*))

Re: link issue

Submitted by axel on Tue, 27/03/2012 - 17:37.

Hi,

Thanks for your report - should be fixed! But please future report bugs at our bug tracker.

Cheers, Axel.

cling.exe hangs up ...

Submitted by Vladimir (not verified) on Thu, 23/02/2012 - 15:33.
I use win32 compiled cling.exe, it hangs up in the simplest cases: int i=1; - OK int i=1 - without ";" - hangs up ++i; - OK ++i - hangs up #include "stdio.h" - OK #include "math.h" - hangs up #include "math_not_exist.h" - OK, informs about error What going wrong in these cases ? Thanks, Vladimir

Re: cling on Windows

Submitted by axel on Thu, 23/02/2012 - 18:21.

Hi Vladimir,

Thanks for your report! C++ on Windows is still only rudimentary supported by clang. And cling depends on clang. The available features have already much improved over the last few months - but e.g. the ValuePrinter template instantiation (needed to print the value of the expression when omitting the ';') still causes an infinite loop on Windows. That's Vassil's diagnosis.

As templates are pretty fundamental for C++, and as work on the Windows C++ ABI has been picked up recently, there is hope that this will get fixed in the near future. We at CERN also need cling to work on Windows...

On Windows, today, cling should work in C-mode (cling -x c).

Cheers, Axel

Hi Axel, I'm a bit confused.

Submitted by Anonymous (not verified) on Fri, 24/02/2012 - 07:35.
Hi Axel, I'm a bit confused. Please clarify what options I have now to use cling in production win application ? As far as I understood in both win32 and win64 cases I can use C language only (until clang will fully support C++ in win32 and win64). It means that I should write C wrappers for C++ DLLs and any C++ code that I want to embed ? Another critical issue, you wrote that there is a critical bug that will be fixed in the nearest 4 weeks - cling sometimes crashes in the end of parsing... Is it applicable for win32/win64 C too ? Thanks, Vladimir

Re: cling on Windows

Submitted by axel on Fri, 24/02/2012 - 20:44.

Hi Vladimir,

As I said, I expect cling on Windows to only work in C mode for the time being. The other bug will affect cling on Windows, too, whether C mode or not - it's about input buffer handling which is the same everywhere. I hope that clarifies the situation. As it is right now I would not recommend cling for production use on Windows. But I cannot predict how long it will take clang to support (most of) Windows C++ ABI: could be months, could be days.

Cheers, Axel

"using namespace std" and c++11 lambdas don't work?

Submitted by Jason (not verified) on Fri, 17/02/2012 - 03:10.
On MacOSX 10.6.8, on on llvm/clang svn r150068; on cling svn r43013, with the patch below to cling/lib/Interpreter/DynamicLookup.cpp:419 to get compilation, I'm getting a crash when I do "using namespace std". 
$ ./cling
**** Welcome to the cling prototype! ****
* Type C code and press enter to run it *
* Type .q, exit or ctrl+D to quit       *
*****************************************
[cling]$ #include iostream   // NB: the html wouldnt let me send angle brackets around iostream, but they were there!
[cling]$ using namespace std;
Declaration name has no FETokenInfo
UNREACHABLE executed at DeclarationName.cpp:339!
Illegal instruction

$ cd ~/pkg/llvm-post-3.0-svn/llvm/tools/cling/lib/Interpreter

# patch previously mentioned... to get compilation.
$ svn diff
Index: DynamicLookup.cpp
===================================================================
--- DynamicLookup.cpp	(revision 43039)
+++ DynamicLookup.cpp	(working copy)
@@ -416,7 +416,7 @@
           // resolution of the constructors and then initializes the new
           // variable with it
 	  ExprResult InitExprResult 
-	    = m_Sema->ActOnParenListExpr(m_NoSLoc,
+	    = m_Sema->ActOnParenOrParenListExpr(m_NoSLoc,
 					 m_NoELoc,
 					 move_arg(Inits));
           m_Sema->AddInitializerToDecl(HandlerInstance,

...also the C++11 lambda feature doesn't seem to work; any clue why? (see below for example)

Thanks!

Jason 

$  ./cling -Wc++11-extensions

**** Welcome to the cling prototype! ****
* Type C code and press enter to run it *
* Type .q, exit or ctrl+D to quit       *
*****************************************
[cling]$ #include 
[cling]$ using std::cout
[cling]$ auto func = [] () { cout << "Hello world"; };
input_line_6:2:2: warning: 'auto' type specifier is a C++11 extension [-Wc++11-extensions]
 auto func = [] () { cout << "Hello world"; };
 ^
input_line_6:2:14: error: expected expression
 auto func = [] () { cout << "Hello world"; };
             ^
[cling]$

Re: using namespace std

Submitted by axel on Fri, 17/02/2012 - 14:57.

Hi Jason,

I have converted your comment into this bug report. Thanks! Note that it does work if you toggle to .rawInput for the using directive using namespace std; - but that's just a woraround.

The mismatch in DynamicLookup.cpp should get fixed later.

Cheers, Axel

Re: Lambda expressions

Submitted by axel on Fri, 17/02/2012 - 14:50.

Hi Jason,

Thanks for your feedback; the compilation problem will get fixed today!

Regarding the lambda, you first need to enable the C++11 standard (you just enabled a warning kind): 

$ cling -std=c++11
[cling]$ #include <iostream>
[cling]$ auto func = [] () { std::cout << "Hello world"; };
input_line_5:2:14: error: lambda expressions are not supported yet
 auto func = [] () { std::cout << "Hello world"; };
             ^
Now if you look at the implementation status of lambdas in clang you will see that this is expected. If you want, help the clang guys implement it and we will all benefit from it! :-)

Cheers, Axel

small adjustment needed to compile DynamicLookup.cpp

Submitted by Jason (not verified) on Fri, 17/02/2012 - 02:42.
A quick patch suggestion: Using what seemed to be the latest cling (svn 43039), and the llvm/clang svn r150068 named in LastKnownGoodLLVMSVNRevision.txt, I had to make the following change to the file cint/cling/lib/Interpreter/DynamicLookup.cpp in order to get compilation:

Regards,
Jason 

svn diff

=====================
--- DynamicLookup.cpp   (revision 43039)
+++ DynamicLookup.cpp   (working copy)
@@ -416,7 +416,7 @@
           // resolution of the constructors and then initializes the new
           // variable with it
          ExprResult InitExprResult
-           = m_Sema->ActOnParenListExpr(m_NoSLoc,
+           = m_Sema->ActOnParenOrParenListExpr(m_NoSLoc,
                                         m_NoELoc,
                                         move_arg(Inits));
           m_Sema->AddInitializerToDecl(HandlerInstance,



svn info
Path: .
URL: http://root.cern.ch/svn/root/trunk/cint/cling/lib/Interpreter
Repository Root: http://root.cern.ch/svn/root
Repository UUID: 27541ba8-7e3a-0410-8455-c3a389f83636
Revision: 43039
Node Kind: directory
Schedule: normal
Last Changed Author: vvassilev
Last Changed Rev: 42986
Last Changed Date: 2012-02-13 13:20:45 -0600 (Mon, 13 Feb 2012)

Re: trunk

Submitted by axel on Fri, 17/02/2012 - 18:39.

Hi Jason,

Thanks to Vassil this is now fixed, including a proper llvm / clang revision number that works. Again, thanks for your report!

Cheers, Axel

Multi-line mode

Submitted by Vladimir (not verified) on Wed, 15/02/2012 - 13:00.
I think cling multi-line mode could be less clever, enough to have the following: Enter - expression is fully entered Enter+Shift - expression will be continued in the next line Enter and Enter+Shift - used widely in editors so user is familiar with them

Re: multi-line mode

Submitted by axel on Wed, 15/02/2012 - 14:59.

Hi Vladimir,

Thanks for your suggestion! Another option would be start editor-like behavior, where one moves up and down with the cursor keys, until one sends off the input using shift- or ctrl-enter. What do you think?

Note: this is just brainstorming - I'm not claiming that we have the time to implement it in 2012 :-) But if somebody is looking for something to contribute then this could be a nice extension!

Cheers, Axel

I think cling standalone is

Submitted by Vladimir (not verified) on Thu, 16/02/2012 - 08:24.
I think cling standalone is mainly for evaluating and studying cling before making decision to use it ? Everybody can wrap cling API with rich editor in some way. So, if I understand cling usage correctly, it could be simple as possible with intuitive commands that don't require long explanations so all set of available commands could be printed in the welcome part. Generally current set of commands seem OK, especially I like the last ";" - print/don't print results. There is only 1 problematic thing - multi-line mode, I think Enter / Enter+Shift is the simplest solution from usability point of view.

re: cling binary

Submitted by axel on Thu, 16/02/2012 - 14:46.

Hi Vladimir,

There are several possible modes of using the cling binary; for your context it's probably for evaluation. Yes, we need ".help". You do know that cling can run (.x) text files, too, right? For complex input that's usually what people do.

Just to remind you: we are building on almost two decades of experience with CINT, and it being used in production by tens of thousands of people. So when I say "people usually edit files" then that's the result of this experience :-) But that doesn't stop us from making fundamental changes, so who knows: if someone designs (with us) and contributed a nice multiline mode I wouldn't mind uploading it!

Cheers, Axel

cling compilation error

Submitted by Vladimir (not verified) on Mon, 13/02/2012 - 17:01.
Today I got llvm, clang and cling according the build instructions and tried to compile all in VS2008. All were enough smoothly excluding 1 compilation error in cling, DynamicLookup.cpp: method m_Sema->AddCXXDirectInitializerToDecl(...) is not defined in clang::Sema It's really not defined and seems the latest cling and clang sources are not synchronized ? How it can be fixed ? Thanks, Vladimir

Cling Compilation

Submitted by vvassilev on Mon, 13/02/2012 - 20:27.
Hi,

Keeping cling in sync with two repos is not an easy job :) I believe it is fixed now!

Cheers, Vassil

cling compile 2 days later ;)

Submitted by Matt Benjamin (not verified) on Wed, 15/02/2012 - 20:46.
Hi, I'm also trying to build Cling, getting this: llvm[2]: Linking Debug+Asserts executable cling /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeMBlazeAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeSparcAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeXCoreAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeARMAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeMipsAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializePTXAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeMSP430AsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeCellSPUAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializePowerPCAsmPrinter' /home/matt/dev/llvmbuild/Debug+Asserts/lib/libcling.so: undefined reference to `LLVMInitializeHexagonAsmPrinter' collect2: ld returned 1 exit status make[2]: *** [/home/matt/dev/llvmbuild/Debug+Asserts/bin/cling] Error 1 make[2]: Leaving directory `/home/matt/dev/llvmbuild/tools/cling/tools/driver' make[1]: *** [all] Error 1 make[1]: Leaving directory `/home/matt/dev/llvmbuild/tools/cling/tools' Any ideas? Thanks!

Re: targets=host!

Submitted by axel on Thu, 16/02/2012 - 14:39.

Hi Matt,

You must configure with --enable-targets=host, else you will pull in all possible targets. As you are the second one reporting this we should probably work around that on the cling side...

Cheers, Axel.

Thank you !

Submitted by Vladimir (not verified) on Wed, 15/02/2012 - 10:10.
Big Thanks ! It's fixed and can be compiled ! I think cling svn should contain compatible llvm and clang versions too for cases if cling temporarily not synchronized with them.

Re: last good revsision

Submitted by axel on Wed, 15/02/2012 - 14:54.

Hi Vladimir,

I prefer not to include llvm + clang in cling's repository. Instead cling now contains a file "LastKnownGoodLLVMSVNRevision.txt" which holds the highest revision number that is known to work. It gets updated by the Makefile, so there is a reasonable chance that this number stays relevant. Thanks for your suggestion!

Cheers, Axel

Is cling stable enough to be used in production application ?

Submitted by Anonymous (not verified) on Sat, 11/02/2012 - 17:40.
Hello, I'm searching a suitable scripting engine for a production application, what's status of cling, is it enough stable for this ? Can it be embedded into a Windows x64 application ? Thanks, Vladimir