|
From: | Brian Callahan |
Subject: | Re: An Issue With Execute Alternate Under OpenBSD, Library Suggestions, and Debugging Help |
Date: | Sun, 23 Feb 2020 09:42:26 -0500 |
User-agent: | Mozilla/5.0 (X11; OpenBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 |
The latest version (SVN) of GNU APL compiles out of the box on OpenBSD. You may want to install the following packages before building: execinfo fftw3 gtk+3 pcre2 You should run the configure script as follows:CC=cc CXX=c++ CPPFLAGS="-I/usr/local/include -I/usr/X11R6/include" LDFLAGS="-L/usr/local/lib -L/usr/X11R6/lib" ./configure
On 2020-02-23 9:37 AM, Brian Callahan wrote:
Hi Jürgen -- Yes, exactly.I have found that the GNU APL configure script doesn't always discover the /usr/local directory (or our /usr/X11R6 directory, where X libraries live). So to be safe, the OpenBSD package of GNU APL (which I tie to releases) does this: CPPFLAGS='-I/usr/local/include -I/usr/X11R6/include' LDFLAGS='-L/usr/local/lib -L$/usr/X11R6/lib' ./configure~Brian On 2020-02-23 9:31 AM, Dr. Jürgen Sauermann wrote:Hi Brian, thanks. If it is installed then the ./configure of GNU APL should detect it and automatically add the proper linker flags. So 'Programmer' should: 1. install the libexecinfo package 2. re-run ./configure 3. make ; make install On 2/23/20 1:43 PM, Brian Callahan wrote:execinfo.h absolutely does exist on OpenBSD. You need to install the libexecinfo package then link with -lexecinfo ~Brian On 2020-02-23 4:20 AM, address@hidden wrote:I've constructed a basic example which crashes GNU APL under OpenBSD; it explains the cause, but the notice may still be valuable: '1'⎕EA'1÷0' Cannot show function call stack since execinfo.h seems not to exist on this OS (WINDOWs ?). Process apl finished I'm also interested in having some of my programs listed in the GNU APL Community page. Follows are the relevant pages; there's another article, 2017-02-02, but this may be considered too vulgar: http://verisimilitudes.net/2019-08-08 gopher://verisimilitudes.net/12019-08-08 http://verisimilitudes.net/2019-12-06 gopher://verisimilitudes.net/12019-12-06 My relevant code should all be classified as L1 portability, as I strive for portable and so correct APL programs. The programs are all licensed under the AGPLv3. Another reason I send a message here is because I'm having issues debugging my 2020-02-20, which I'd also care to have included once I've finished correcting it. The ⎕TRACE doesn't provide enough information for me and I'm unaware of how to properly use ⎕STOP, managing to crash GNU APL under OpenBSD whilst using it. I'd appreciate help in using these two commands to their fullest, if one is willing to offer it.
[Prev in Thread] | Current Thread | [Next in Thread] |