attached it the stace log for script with just ⍳10001 in it on 1474
strace-log
Description: Binary data
Hello
i was able to compile the apl/libapl 1474 on a number of different computers
and all exhibit the same problem with doing ⍳10001 in ws/script/libapl c code
32 bit debian vitural in a 32 bit linux/intel cpu
64 bit debian on rasp p/rpi3b/arm64
64 debian on amd64
32 bit linux on 64bit hp/in
Hello
From the make install the APserver is in /usr/local/bin/APserver along with
apl and AP100 and AP210
but according to the strace log it never looks for /usr/local/bin/APserver just
in the current dir
access("./APserver", X_OK) = -1 ENOENT (No such file or directory)
acces
Hello
building libapl in a clean directory does the trick
i didn't notice that the make distclean quits with the following
make[2]: *** No rule to make target
`sql/.deps/libapl_la-SqliteResultValue.Plo'. Stop.
make[2]: Leaving directory `/src/apl/1474/apl-1474/src'
make[1]: *** [distcle
Hi Kacper,
thanks. I have updated the GNU APL home page, now pointing out
that tarballs are not
the preferred way of installing GNU APL.
Best Regards,
Jürgen
On 6/18/21 10:47 PM, Kacper Gutowski
wrote:
On Fri, Jun 18,
Hi,
at a first glance:
You cannot simply skip init_libapl() because that will
leave many
C++ variables undefined and because of that your program will
crash
sooner or later.
Instead: make sure your program finds the APserver
