[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: yet another ddd 3.3.12 MacOS Xt error
From: |
rbd |
Subject: |
Re: yet another ddd 3.3.12 MacOS Xt error |
Date: |
Fri, 18 Nov 2016 08:13:12 -1000 (HST) |
User-agent: |
Alpine 2.20 (OSX 67 2015-01-07) |
Hi all,
I do still have one remaining Mac with a still-working ddd (i.e.,
with no fatal Xt inheritance error as reported frequently here) running
older system software. Here is a comparison of relevant software releases
installed on that system and one of my no-longer-working machines:
Still working with no fatal Xt inheritance error:
Yosemite 10.10.5
XQuartz 2.7.8 (xorg server 1.16.4)
MacPorts 2.3.3, including the following port packages:
ddd 3.3.12_2
openmotif 2.3.4_2
xorg-libXt 1.1.4_0
No longer working due to fatal Xt inheritance error:
El Capitan 10.11.6
XQuartz 2.7.11 (xorg server 1.18.4)
MacPorts 2.3.4, including the following port packages:
ddd 3.3.12_3
openmotif 2.3.4_3
xorg-libXt 1.1.5_1+flat_namespace
Seems unlikely that there's been any change in ddd that would have caused
this problem. Also strikes me as unlikely that MacOS or the X server would
be the issue, either. I remain very suspicious of the libXt
+flat_namespace flag now required in the MacPorts install to get openmotif
to subsequently install.
I would be interested to hear from other MacOS ddd users (with either
working or broken systems) with regard to their release levels and install
flags as shown above.
Thanks,
Roger