Re: Apparently libXt isn't actually a leaf on the X11 library tree after all

Jack Howarth <[email protected]>
Newsgroups gmane.os.apple.fink.devel
Message-ID <CAP5Ds0DyArOjsesZ9UzLTLb4rac4rk8KR_vAayx03nK8=mi+CQ@mail.gmail.com>
On Thu, Nov 3, 2016 at 7:56 PM, Hanspeter Niederstrasser
<[email protected]> wrote:
>
> On 11/2/16 6:48 PM, Alexander Hansen wrote:
> > We had thought that libXt wasn’t actually linked in the X11 tree, but this appears not to be so.
> >
> > It’s linked by:
> > /opt/X11/lib/libXaw6.6.dylib
> > /opt/X11/lib/libXaw7.7.dylib:
> > /opt/X11/lib/libXaw8.8.dylib:
> > /opt/X11/lib/libXaw3d.8.dylib:
> > (these may not matter since we’ve got libxaw3dxft2)
> > /opt/X11/lib/libxkbui.1.dylib
> > /opt/X11/lib/libXmu.6.dylib
> >
> > The last one appears to be what is causing runtime failures with xemacs, since xemacs links to /opt/X11/lib/libXmu.6.dylib and to /opt/X11/lib/libXt.6.dylib, along with our libXaw.8.dylib (libxaw3dxft-shlibs) which now links to Fink’s libxt.6.dylib from libxt-shlibs.
> >
> > Unfortunately, the whole rationale for having our own libxt (not so much for libxt-flat) was to try to provide a consistent libXt so that people wouldn’t have things break when updating from Xquartz 2.7.8 to later versions where libXt has been mucked with.
> >
> > Here are some options:
> >
> > 1)  Ditch libxt, possibly libxt-flat, and roll our own Xquartz
>
> I've been keeping an X11 set of packages mostly up to date:
> http://cvs.snaggledworks.com/viewvc.cgi/fink/10.7/main/finkinfo/x11 and
> x11-system directories.
>
> The libraries are current. xorg-server is not current and I haven't used
> it in probably 3 years (and I was running 10.7 at the time). Although it
> ran, there were several things that still needed patching (xinit I
> believe was looking in wrong paths). Also, IIRC, StartupItems behavior
> has changed since then and would probably need to be fixed in these
> packages. Also, there currently is no xorg-libxt-flat package in my set.
>
> I'm agnostic on rolling our own versus forcing an update to 2.7.11. The
> latter is less work, but we are at the mercy of another fix from upstream.
>
> Hanspeter


Hanspeter,
      FYI, I have posted patches for fink to support sandboxing at
https://github.com/fink/fink/pull/135 which will allow you easily
blacklist /opt/X11. The patches use a %p/etc/fink.sb file containing a
simple list of directories to be blacklisted.
         Jack

>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Fink-devel mailing list
> [email protected]
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.devel
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-devel

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.