This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Versioning mess proved!!!
- To: pb at futuretv dot com
- Subject: Re: Versioning mess proved!!!
- From: Geoff Keating <geoffk at cygnus dot com>
- Date: Mon, 2 Oct 2000 12:12:12 -0700
- CC: Franz dot Sirl-kernel at lauterbach dot com, drepper at redhat dot com, howarth at fuse dot net, libc-alpha at sourceware dot cygnus dot com, aj at suse dot de
- References: <E13g34G-0000c4-00@fountain.labs.futuretv.com>
> cc: Ulrich Drepper <drepper@redhat.com>, Geoff Keating <geoffk@cygnus.com>,
> howarth@fuse.net, libc-alpha@sourceware.cygnus.com, aj@suse.de
> From: Philip Blundell <pb@futuretv.com>
> Date: Mon, 02 Oct 2000 11:43:32 +0100
>
> In message <00100212211500.29217@enzo.bigblue.local>, Franz Sirl writes:
> >Maybe the hack is elsewhere already? It turns out that zlib is compiled
> >without -fpic by default, if compiled with -fpic everything is OK. Can't we
> >just refuse to load such broken stuff as shared library on non-x86 platforms?
> >And issue a loader warning on x86 and then delete support for this in
> >glibc-2.3? I believe a -DENABLE_X86_SHARED_LIB_HACKS would clean up our
> >shared lib loader (and probably ld too) from a lot of hacks?
>
> We've had this discussion before. Support for non-PIC shared objects is a
> desired feature, not an x86 hack. It works on platforms like ARM and (I
> guess) Alpha, and I can't see any reason PowerPC should be different.
In any case, the problem is independent of whether the shared object
is PIC or not.
[And, yes, non-PIC shared objects are supported on PowerPC.]
--
- Geoffrey Keating <geoffk@cygnus.com>