similar to: disconnected errors

I was digging through some of the archives and ran into someone who was having the same problem, but for completely different reasons....i think. dovecot: Nov 02 07:58:51 Info: Dovecot starting up dovecot: Nov 02 07:58:52 Error: Auth process died too early - shutting down dovecot: Nov 02 07:58:52 Error: child 27673 (login) killed with signal 11 dovecot: Nov 02 07:58:52 Error: child 27672 (login)

I''m trying to evaluate what use I can make of JIRA with Rails/Ruby and am getting frustrated. The jira4r gem will install but the soap4r gem won''t load. literally: ''irb -r soap4r'' returns :cannot load such file... I also set this up in a Gemfile and tried to run this from the rails console:

Hi Richard, On 7/10/20 11:10 PM, Richard Smith wrote: > Hi Vassil, > > This is a very exciting proposal that I can imagine bringing important > benefits to the existing cling users and also to the clang user and > developer community. Thank you for all the work you and your team have > done on cling so far and for offering to bring that work under the > LLVM umbrella!

On 7/10/20 1:57 PM, Vassil Vassilev wrote: > On 7/10/20 6:43 AM, JF Bastien wrote: >> I like cling, and having it integrated with the rest of the project >> would be neat. I agree with Hal’s suggestion to explain the design of >> what remains. It sounds like a pretty small amount of code. > > >   JF, Hal, did you mean you want a design document of how cling in >

I like cling, and having it integrated with the rest of the project would be neat. I agree with Hal’s suggestion to explain the design of what remains. It sounds like a pretty small amount of code. > On Jul 9, 2020, at 7:25 PM, Hal Finkel via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > I think that it would be great to have infrastructure for incremental C++ compilation,

Motivation === Over the last decade we have developed an interactive, interpretative C++ (aka REPL) as part of the high-energy physics (HEP) data analysis project -- ROOT [1-2]. We invested a significant  effort to replace the CINT C++ interpreter with a newly implemented REPL based on llvm -- cling [3]. The cling infrastructure is a core component of the data analysis framework of ROOT and

OK, I'm actually trying to write something which interacts with IMAP. I'm trying to run the FETCH command and it goes OK, but I'm wondering how I might be able to call both RFC822.SIZE and BODY[HEADERS.FIELDS(..) in the same call. Right now I'm only able to get this to work with two calls to the server. I was hoping to avoid making two calls. Any suggestions? (I realize it

Dear Sir/Madam Our company, 4Js software, has developed an SQL data base software that runs under different operating systems: Windows, Linux, Mac OS X. This software compiles each SQL statement into a C program that is compiled "on the fly" and executed by our JIT, Just In Time compiler. We wanted to port it to Apple's iOS, and spent a lot of time retargetting the JIT for

In the event that I really don''t want a certain model, can I delete it? Is there a tool that I can use besides ''rm'' to ensure I hit everything related to the model? Right now my only guess is to just remove all files that match a filemask and hope for the best.

Hi, I ran into a problem migrating cling (finally!) to MCJIT: When an ("outer") MCJIT's finalization / llvm::RuntimeDyldImpl::resolveExternalSymbols() is called and a symbol is not known, cling can help by loading the suitable library and providing the symbol. It compiles the relevant C++ header as part of loading the library. This compilation emits symbols through the MCJIT. That

On Thu, Jun 12, 2014 at 10:57:46AM +0200, Armin Steinhoff wrote: > > Hi, > > first problem was: > > >FileManager.cpp:311:21: error: range-based ‘for’ loops are not allowed > >in C++98 mode > >for (auto & fe: SeenFileEntries) { > >^ > >FileManager.cpp:312:14: error: request for member ‘getValue’ in ‘fe’, > >which is of non-class type ‘int’

Hi Lang, thank You very much. I've used Your code and the creating of the object file works. I think the problem is after creating the object file. When I link the object file with ld I get an executable, which is working right. After changing the clang and llvm libraries from the package control version (.deb) to a own compiled version with debug options, I get an assert() fault. In void

Dear LLVM-Developers and Vinod Grover, we are trying to extend the cling C++ interpreter (https://github.com/root-project/cling) with CUDA functionality for Nvidia GPUs. I already developed a prototype based on OrcJIT and am seeking for feedback. I am currently a stuck with a runtime issue, on which my interpreter prototype fails to execute kernels with a CUDA runtime error. === How to use the

well, with some help I've made a fair amount of progress on my box. It's working out much easier than I had anticipated and perhaps my notes will be useful some day. I have two questions... Here is where I am: cling:~# egrep -v "^($|\#)" /etc/dovecot.conf protocols = imap imaps login = imap login_max_processes_count = 16 login = pop3 max_mail_processes = 512

On Jul 8, 2008, at 4:57 AM, Chris Lattner wrote: > On Mon, 7 Jul 2008, David Greene wrote: >>> Since I think it really is a part of the LLVM internals, I don't >>> think >>> that mangling it with a prefix is the right way to go. This would >>> significantly increase verbosity in the code and would be generally >>> detrimental. >>

I was upgrading my debian box and managed to upgrade my dovecot installation at the same time. I wasn't planning on it, but it came along just the same. I took some notes on what I thought I needed to change, but apparently it wasn't enough. I've been running this for quite some time now with pgsql authentication and it's been one of those nice applications that always

Indeed ld does link it. The reason I am using llvm-ld, is for its unique functionality. I intend to link to object files together (created by cling), and link them with llvm-ld. The main feature that I am currently interested in is the ability to have "inline functions" between two object files. This was basically impossible with gcc. Is there any way to make the raw binary with llvm?

I do not know enough about cling, but I like what you describe very much, am particularly intrigued about how your approach could also be appropriated to do ahead-of-time constexpr metaprogramming as well, which also involves incrementally adding declarations to the translation unit. Dave > On Jul 9, 2020, at 11:43 PM, JF Bastien via cfe-dev <cfe-dev at lists.llvm.org> wrote: > >

Hello: I am told that compile cling, from CERN, I need revision 165095. HOW do I check out that version? When going through the /tags directory, all version are 17xxxx. I tried svn checkout -r 165095 http://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx llvm but it will not work with either /truck or /tags I tried svn checkout http://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx at 165095, but that also doen't work

Hi, I'm finally moving cling to MCJIT - and MCJIT is wonderful! So far I only ran into this issue: $ cat linkonceodr.cxx extern "C" int printf(const char*,...); template <class T> struct StaticStuff { static T s_data; }; template <class T> T StaticStuff<T>::s_data = 42; int compareAddr(int* mcjit); #ifdef BUILD_SHARED int compareAddr(int* mcjit) { if (mcjit