Path: utzoo!utgpu!watserv1!watmath!att!att!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvlx!tomg
From: tomg@hpcvlx.cv.hp.com (Thomas J. Gilg)
Newsgroups: comp.sys.apollo
Subject: Re: Position Independent Code and Xt library
Message-ID: <101020012@hpcvlx.cv.hp.com>
Date: 24 Nov 90 03:14:49 GMT
References: <1990Nov20.011628.8963@metro.ucc.su.OZ.AU>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 22


> Problems start if one now wants to include a library in the
> link step. Quick check of the stuff in /usr/lib/X11 shows that
> libX11.a and libXt.a are not PIC. However, linking with libX11
> still gives a PIC file, but linking with libXt gives a non-PIC
> file. In fact NONE of the constituent files in libXt are PIC.

First, to my knowledge all archived libraries in /usr/X11/lib should be
non-PIC for performance reasons.  Second, you should be referencing
/lib/x11lib and /lib/xtlib via  -A inlib,/lib/whatever  in your link
line.

> What's going on here? Can I link with libXt and still 
> end up with a module which can be dynamically loaded or is this
> just impossible?  How come libX11 doesn't cause this problem? 

I've noticed that the "x11lib" entry in /etc/sys.conf results in all types
of mystifying link magic.  You might not be linking against what you
think you are.

Thomas Gilg
tomg@cv.hp.com