Including non-PIC code in a shared library?
Hi,
I finally got packages of libGGI built and uploaded. I was quite pleased
to find that the generic debian/rules that I've been using for the last
9 months really -does- work correctly for multiple binary packages.
I always thought it would, but never had a multi-binary package to try
it on. ;-)
But, to the point. LibGGI has various display "targets", each
of which is kept in a separate *.so file under /usr/lib/ggi/.
The problem is that the "xf86dga" target contains code linked in from
/usr/X11R6/lib/libXxfs86{dga,vm}.a. This code in compiled non-PIC, and
lintian complains about it; that's why the xf86dga target is missing in
the current release, ICYWW.
I asked about this on ggi-devel, and the responses I got indicated that
it probably wasn't a problem, because there would only ever be one
libGGI program running the xf86dga target at once on a given machine
(not true for multi-headed machines) and that if multiple copies were
run, the kernel would simply load multiple copies of the code. I'm a
little worried that mixing PIC and non-PIC code might do some other harm.
Does it? Or will it just make this "shared" object unsharable?
Thanks,
--
Charles Briscoe-Smith
White pages entry, with PGP key: <URL:http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: