From xemacs-m  Mon Jun 30 09:23:37 1997
Received: from firewall2.Lehman.COM (firewall.Lehman.COM [192.147.65.67])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id JAA18502
	for <xemacs-beta@xemacs.org>; Mon, 30 Jun 1997 09:23:36 -0500 (CDT)
Received: (from smap@localhost) by firewall2.Lehman.COM (8.8.5/8.6.12) id KAA23480 for <xemacs-beta@xemacs.org>; Mon, 30 Jun 1997 10:23:36 -0400 (EDT)
Received: from unknown(146.127.39.20) by firewall2 via smap (V1.3)
	id tmp023462; Mon Jun 30 10:23:35 1997
Received: from cfdevx1.lehman.com by relay.lehman.com (4.1/LB-0.6)
	id AA10504; Mon, 30 Jun 97 10:23:34 EDT
Received: from localhost by cfdevx1.lehman.com (4.1/Lehman Bros. V1.6)
	id AA17694; Mon, 30 Jun 97 10:23:33 EDT
Message-Id: <9706301423.AA17694@cfdevx1.lehman.com>
Reply-To: Rick Campbell <rickc@lehman.com>
X-Windows: Don't get frustrated without it.
Organization: Lehman Brothers Inc.
From: Rick Campbell <rickc@lehman.com>
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Solaris dynamics?
X-Pgp-Version: 2.6.2
X-Pgp-Signed: iQCVAwUBM7fBXVtTztlqB385AQFxOwP/eJXE7jusemSTKy7Wve+sCc49OcuXLMdB
	      1wReN/HY2s32ifH9iaclIjfLeIV2q/TkVSfIyco8k/4KrOSYyEYIiK72kMNTGaTZ
	      etgIrqaKcFQCHrCZqzHSDu2ePftK716OcohXko1lIGHhd5G3PTy9o3rsWkD5UEiP
	      lm30gliC+wk=
	      =B1CT
Date: Mon, 30 Jun 1997 10:23:31 -0400
Sender: rickc@lehman.com

So, I've been trying to get used to Solaris and the fact that it's
almost as bad as NT when it comes to using dynamic linking all over
the place so that a heterogeneous environment requires that almost
every application has it's own LD_LIBRARY_PATH, but I thought that
XEmacs builds were generally set up to handle versioning by using the
oldest version in creation when building something -- never mind I
think that such a protocol is a great indication that an underlying
mechanism is severely, uh, flawed.

Anyway, when I try to run the prebuilt 19.15, I get an error message
about not being able to find libXm.so.3 and sure enough, what's in my
path is libXm.so.2.  Is there any way that I can run the prebuilt
XEmacs under Solaris?

Is there any chance that policy can be changed so that the prebuilt
XEmacs binaries are portable.  In particular, can the policy be that
a staticly linked version is made available for people who don't have
the particular mix of shared libraries that existed in the build
environment?

On a related note, is it even possible to build things completely
statically on the latest Sun operating systems?  I'm getting the
impression that they're doing everything possible to rule out that
option altogether.  It makes me think that it would be almost
impossible to distribute a secure application over even a relatively
limited network if you couldn't know exactly what code would be
executed at run-time.

			Rick

