[Bug 2739] StaticNeedsPicForShared YES is often required on x86

[bugzilla-daemon at freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=2739          
     




------- Additional Comments From mharris at www.linux.org.uk  2005-03-19 00:30 -------
That may be so, but either X.Org CVS has this turned on by default so
that software compiles correctly on x86, or else every distribution known
to man, shipping a modern KDE and other software which links shared libs
to static X libs will not work properly.  I suppose another solution is
to provide shared versions of all libraries included, so that these libs
link to the shared versions instead.  That is done for most libs now,
but there are some left that don't do it.

I'm going to disable StaticNeedsPicForShared in our spec file and wait to
see what breaks.  I'll send out a notice to our devel mailing list for
people to rebuild things that link to X libraries to see if they fail
without PIC shared libs or not, and provide feedback back here.

There might be other solutions we could consider if the problem is still
as prevalent as it was since around 4.3.0 or so.

I'm not sure what this has to do with libGL though, it is perfectly fine
as is.  Also, Jakub's original libGL patches reduced the number of
symbols needing relocations by marking symbols private that were internal.
It made it possible to make libGL PIC *without* performance problems,
because the performance critical code wasn't hit.

I never did understand why Jakub's patches were rejected outright and
reimplemented by other people.  I don't know if the alternative
implementations did all of the things that Jakub's patches did, so
I don't know if libGL would be negatively affected by building it
PIC now or not.
          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.