search for: dlloading

can anyone help with this??? /!\ FAILSAFE /!\ Thu Apr 08 16:58:27 -0700 2010 Status: 500 Internal Server Error unknown error C:/Ruby/lib/ruby/1.8/dl/import.rb:29:in `initialize'' C:/Ruby/lib/ruby/1.8/dl/import.rb:29:in `dlopen'' C:/Ruby/lib/ruby/1.8/dl/import.rb:29:in `dlload'' C:/Ruby/lib/ruby/1.8/dl/import.rb:27:in `each''

...with undefined symbols if they choose not to compile against that library)? That is, I'm trying to see what you are considering to be a break between: - what we have now: nbdkit-file-plugin.so: depends on nbdkit_realpath() as undefined symbol nbdkit binary: provides nbdkit_realpath() before dlloading the plugin - building with -no-undefined libnbdkit.so: provides nbdkit_realpath() nbdkit binary: depends on libnbdkit.so, making nbdkit_realpath() available nbdkit-file-plugin.so: depends on libnbdkit.so, so it sees nbdkit_realpath() - out-of-tree with undefined symbol libnbdkit.so: provides nbdk...

On Tue, Mar 24, 2020 at 02:16:32PM -0500, Eric Blake wrote: > On 3/24/20 1:54 PM, Richard W.M. Jones wrote: > >On Tue, Mar 24, 2020 at 01:43:52PM -0500, Eric Blake wrote: > >>On 3/21/20 7:06 AM, Richard W.M. Jones wrote: > >>>Eric: > >>> > >>>Yifan Gu has posted a few patches for mingw support. My comments > >>>below. >

On Sat, Sep 21, 2019 at 09:45:16PM +0200, Martin Kletzander wrote: > On Sat, Sep 21, 2019 at 03:54:11PM +0100, Richard W.M. Jones wrote: > >On Fri, Sep 20, 2019 at 09:33:06AM -0500, Eric Blake wrote: > >>Checking for file existence for filters is somewhat less fragile than > >>for plugins, because all filters are built in-tree (we've specifically >

I''ve created a simple hello world app that doesnt appear to serve up the view greeting.rhtml. :< Any ideas ? The error message is from development.log is... # Logfile created on Tue Aug 18 16:49:55 -0400 2009/!\ FAILSAFE /!\ Tue Aug 18 16:50:34 -0400 2009 Status: 500 Internal Server Error unknown error PS . It does show the default web page ok at http://localhost:3000 just not

Hi Olivier, On Feb 25, 2010, at 14:10, Olivier Meurant wrote: > Hi Garrison, > > I finally come back from holidays and take time to watch your patch. > > I must say that I largely prefer this version over the previous one ! I like the reuse of getLazyFunctionStub, but I don't know if the forceEmitFunctionStub is still needed ? JIT::forceEmitFunctionStub(...) was created to

Hello, For a course project, I am required to write a compiler for some language of my choice, and this compiler has to be implemented in a functional language. I have chosen create a *JIT* compiler for C source, and to implement my compiler in OCaml using LLVM for the back-end. I have experience using LLVM in C++ (I wrote a MATLAB JIT compiler not long ago), however, I am a bit puzzled as to how

Hi Garrison, I finally come back from holidays and take time to watch your patch. I must say that I largely prefer this version over the previous one ! I like the reuse of getLazyFunctionStub, but I don't know if the forceEmitFunctionStub is still needed ? I thought about JIT and modules, and I wonder if we don't need to take it another way. Now we can create multiples JIT. What if we

Is there anything in the utils to capture a screen ( or maybe just a window) and save to a file. I have this, but I have no idea where it came from, but it gives a corrupted image Paul # -*- ruby -*- # screen capture -- # This script runs with a Ruby/DL which is included in ruby-1.7. require ''dl/import'' module ScreenCapture extend DL::Importable dlload

This is the second version of a patch, which I recently attached to bug 2606, whose original version was modified to reflect the lists comments. Also please note the comment at the end of this email, which basically questions whether this bug is really a bug. 1) To solve the foreign Module GlobalVariable problem, I modified JIT::getOrEmitGlobalVariable(...) to directly attempt to map a found