🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.windows.x
Article #37751

Re: xterm, xload, and X libraries in non-standard locations

#37751
From: David C Lawrence
Date: Wed, 07 Mar 1990 01:42
21 lines
1190 bytes
In <9003061606.AA17990@nswc-wo.arpa> cwarsaw@NSWC-WO.ARPA (Warsaw):

> According to the ERRATA, xterm and xload must be linked statically.

Only if you make them setuid to root.  You don't have to do that at
all with xload to get full functionality and you (well, I) can live
without it with xterm.  Nevertheless ...

> Is there a flag I can set in their Imakefile's so that this is automatic?

In xterm's Imakefile I think you can put in a line

LDOPTIONS = -Bstatic $(CDEBUGFLAGS) $(CCOPTIONS)

and it should link statically.  This will happen for "resize" too.

For xload, chgrp it to the group that owns /dev/kmem (standard is "kmem",
gid 2, on SunOS 4 systems) and make the executable setgid.  Make sure
that /dev/kmem is readable by the group.

Dave
Technical Details
Message-ID: <ZS-##4=@rpi.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!tale
References: <9003061606.AA17990@nswc-wo.arpa>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!tale
From: tale@cs.rpi.edu (David C Lawrence)
Newsgroups: comp.windows.x
Subject: Re: xterm, xload, and X libraries in non-standard locations
Message-ID: <ZS-##4=@rpi.edu>
Date: 7 Mar 90 01:42:04 GMT
References: <9003061606.AA17990@nswc-wo.arpa>
Organization: Rensselaer Polytechnic Institute, Troy NY
Lines: 21