Re: ECL + EQL Standalone Binary

2017-09-26 Thread Joshua Kordani
So your binary is looking for whatever version of ecl lives at @libdir@/libecl.16.1.dylib.  I still can't find a definition for the macros, but this

Re: "Got signal before environment was installed on our thread"

2017-09-26 Thread Dima Pasechnik
Discussing the issue with GC people here https://github.com/ivmai/bdwgc/issues/180 On Fri, Sep 22, 2017 at 1:14 PM, Daniel Kochmański wrote: > On 22.09.2017 13:31, Dima Pasechnik wrote: >> >> No, we have not done that before, and everything worked on Linux and >> OSX, and even on Cygwin (that is

Re: ECL + EQL Standalone Binary

2017-09-26 Thread Joshua Kordani
I cant speak to whether or not ecl is correctly built, but what is the output of otool -L on your app binary? On 9/26/17 12:32 PM, John Mercouris wrote: Hi Joshua, sorry for the double email, it occurred to me to list the dependencies as well: > otool -L libeql5.1.0.0.dylib libeql5.1.0.0.dyl

Re: ECL + EQL Standalone Binary

2017-09-26 Thread John Mercouris
Hi Joshua, sorry for the double email, it occurred to me to list the dependencies as well: > otool -L libeql5.1.0.0.dylib libeql5.1.0.0.dylib: libeql5.1.dylib (compatibility version 1.0.0, current version 1.0.0) @libdir@/libecl.16.1.dylib (compatibility version 16.1.3, current ve

Re: ECL + EQL Standalone Binary

2017-09-26 Thread John Mercouris
Hi Joshua, Very interesting article that you sent, interested in seeing exactly what the shared libraries were reporting as their names, I got the following: > otool -D libecl.16.1.3.dylib libecl.16.1.3.dylib: @libdir@/libecl.16.1.dylib > otool -D libeql5.1.0.0.dylib libeql5.1.0.0.dylib: libeql

Re: ECL + EQL Standalone Binary

2017-09-26 Thread Joshua Kordani
The behavior you're seeing r.e @executable_path et al is osx behavior.  I can't find a list of all of the supported "macros" but this gives an example of what is going on. Loosely, executables have the paths to the dylibs th

Re: ECL + EQL Standalone Binary

2017-09-26 Thread John Mercouris
Hi Paul, I’ve commented out the line: EQL::ini(argv); But I still haven’t had any luck with the standalone binary. I can get compilation to work if I don’t move my dylibs into my application bundle. The problem is that it’ll run just fine on my computer, but I can’t easily distribute it becaus

Re: ECL + EQL Standalone Binary

2017-09-26 Thread Joshua Kordani
John, I think Pascal means that you will need to use (cffi:load-library "path/to/library") in your code, and if you happen to bundle your dylibs with your .app then you can at least find them there.  One problem that I haven't found a good answer to is if your libs have explicit path referenc

Re: ECL + EQL Standalone Binary

2017-09-26 Thread PR
2017-09-25 19:19 GMT+02:00, John Mercouris : > Any ideas on how to proceed would be very useful, thank you, Another (generic) observation: It seems that your terminal uses a debugger (automatically?). If I want to use gdb on Linux, I need a ~/.gdbinit file with these lines: handle SIGPWR nost