| Hi John:
No need to apologize. We all learned something…. Maybe a note can be added to the README or the info documentation or something.
IME it’s been pretty reliable.
As to learning the GNU build system. It’s the devil's nightmare IMO. Anything beyond ./configure, make, make install, is not worth the intellectual energy. (Unless you already are a veteran autotools user.)
If all you want to do is build GNU APL on Mac just use Jürgen's production.
Then spend the rest of your time learning APL. That will be more enjoyable and productive.
OTOH if you want to produce your own SW that is cross platform use Xcode and CMake.
my 02¢
respect…
Peter
Thanks, Peter. I'm sorry to learn you reproduced the issue. I'll
keep poking on my end as time permits. I have not dug into how the
GNU build system really works, so my progress will probably not be
fast. /John
On 3/18/21 10:52 PM, Peter Teeson
wrote:
P.S. Gandalf:~ pteeson$
ls -al /usr/X11
lrwxr-xr-x
1 root wheel 8 9 Jul 2020 /usr/X11 -> /opt/X11
Gandalf:~ pteeson$ ls -al /opt/X11
total 0
drwxr-xr-x 9 root wheel 288 27 Sep 2016 .
drwxr-xr-x 3 root wheel 96 26 Sep 2016 ..
drwxr-xr-x 128 root wheel 4096 9 Jul 2020
bin
drwxr-xr-x 4 root wheel 128 29 Oct 2016
etc
drwxr-xr-x 19 root wheel 608 9 Jul 2020
include
drwxr-xr-x 204 root wheel 6528 9 Jul 2020
lib
drwxr-xr-x 4 root wheel 128 26 Oct 2016
libexec
drwxr-xr-x 14 root wheel 448 27 Sep 2016
share
drwxr-xr-x 5 root wheel 160 27 Sep 2016
var
Hi John:
Same issue here…(svn 1410) on Mojave
10.14.6.
I have copied the list.
⎕PLOT ''
SYNTAX ERROR+
⎕PLOT ‘'
I searched the bug-app archives and
there was a bunch of emails last summer about
missing X11.
Never use ⎕PLOT myself. But I did
find X11 in my build log:
checking for XGetXCBConnection in
-lX11-xcb... no
checking for XOpenDisplay in
-lX11... no
When I do locate X11 in Terminal I get
this
So maybe that’s the issue?
Need to fix $PATH for GNU APL build??
respect
Peter
Hello Peter -
Please forgive me in
advance for reaching out directly,
but I fear I have a local problem
and don't want to spam the list. I just tried your clone
suggestion below and it fails for
me...
- I built a VMware Fusion
virtual machine with a clean
install of Mojave 10.14.6
- Installed the XCode
command line tools
- Ran: git clone https://git.savannah.gnu.org/git/apl.git
- cd trunk,
followed by ./configure,
make, sudo make install
- Installed the apl
keyboard and tested with ⎕plot
'', which returns a syntax error
instead of the ⎕plot message.
I have repeated this
exercise with High Sierra and
Catalina on physical machines with
the same result. Also, I performed a
MacPorts install on High Sierra and
Catalina on physical machines;
again, with the same result. I spend much of my time in
OS X command shell (iTerm2, to be
specific) and seldom have this much
difficulty doing builds.
Nonetheless, I'm okay with being
guilty of user-error until proven
innocent. In any case it seems clear
that something big-and-basic is
wrong.
Would you be willing to
send me the console log of one of
your successful builds? This would
let me do a diff against my build
logs and possibly give me some clues
as to what I'm doing wrong. Kind regards,
John
On 3/7/21
9:59 PM, Peter Teeson wrote:
Hi Jürgen:
As promised a brief
update note.
On a clean install of
macOS Mojave 10.14.6 I confirm
that using
And with
the default settings the
Terminal waltz builds clean.
And APL executes.
My hardware is an
Early 2009 Mac Pro and so far there has never
been a need
to
patch the installer from 2009 Snow Leopard 10.6
thru to 2018 Mojave 10.14.
I did apply a
patch to the firmware to make it
a 5,1 from the original 4,1.
Will look
into whether it’s reasonable to
install Catalina and Bug Sur.
respect
Peter
|