Hi,
Just to inform what I successfully resolved the issue by running
aclocal, automake and autoconf and reconfiguring && building again.
Br,
/Alexey
Juergen Sauermann writes:
> Hi Alexey,
>
> GNU APL uses the C functions dlopen() to open the library and dlsym() to
> locate functions
> inside
Hi Alexey,
GNU APL uses the C functions dlopen() to open the library
and dlsym() to locate functions inside
the library.
From the printout we see that GNU APL finds the library file but the
dlopen() of the existing file fails.
Although the dlopen()
Hi,
Could you please hint me how to specify these flags so I can experiment
myself?
Br,
/Alexey
2017-12-11 16:19 GMT+01:00 Juergen Sauermann
:
> Hi Alexey,
>
> I suppose that you need some platform specific linker flags when building
> *libemacs.dylib*.
> Since I do not have access to a Mac OS
Hi Alexey,
I suppose that you need some platform specific linker flags when
building libemacs.dylib.
Since I do not have access to a Mac OS-X machine, I can't tell you
which ones.
Best Regards,
/// Jürgen
On 12/06/2
It is really strange but reporting with otool shows two level:
otool -hV /Users/alexey/Applications/gnu-apl/lib/apl/libemacs.dylib
/Users/alexey/Applications/gnu-apl/lib/apl/libemacs.dylib:
Mach header
magic cputype cpusubtype capsfiletype ncmds sizeofcmds flags
MH_MAGIC_64 X86_64
Hi,
from the GNU APL printout it looks like the file was found, but
something is wrong with the file:
file /Users/alexey/Applications/gnu-apl/lib/apl/libemacs.dylib
( flat namespace
in /Users/alexey/Applications/gnu-apl/lib/apl/libemacs
Perhaps adding the path to the dylib file in DYLIB_LIBRARY_PATH will help?
Don't forget to exprt the variable before starting apl.
Regards,
Elias
On 4 December 2017 at 01:56, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
> Hi,
>
> I haven't changed anything in that area. One poster i
Hi,
I haven't changed anything in that area. One poster in one of the
links below mentioned that an OS-X upgrade
had fixed a similar problem that the poster had, so my impression
is that this is a problem than cannot be fixed
inside GNU APL.
10.6.8 is indeed very old. I thought my Macbook was old and it's running
10.10.
I have to admit that I haven't tried the Emacs mode on OSX in a while since
I don't use Macs anymore. That said, last time I did try, it worked fine.
Jürgen, could there be an issue with the way the libraries are buil
Hi Alexey,
I am not really familiar with emacs or OS X, so Elias is probably
better informed than me.
Unfotunately shared libraries are rather platform dependent and so
are the error messages that
they produce. From the output below it seems th
10 matches
Mail list logo
