ldconfig Order.

[Pat Suwalski]

On 10/02/10 01:43 PM, Pat Suwalski wrote:
> This is Debian Squeeze, though Lenny does it as well. My only insight is
> this funny OS ABI flag:
>
>           libGL.so.1 (libc6, OS ABI: Linux 2.4.20) =>  /usr/lib/libGL.so.1
>           libGL.so.1 (libc6) =>  /usr/lib/nvidia/libGL.so.1

Experimentation shows that this is in fact the cause.

I removed the following block (src/mesa/x86/glapi_x86.S):

#if defined(GLX_USE_TLS) && defined(__linux__)
         .section ".note.ABI-tag", "a"
         .p2align 2
         .long   1f - 0f   /* name length */
         .long   3f - 2f   /* data length */
         .long   1         /* note length */
0:      .asciz "GNU"      /* vendor name */
1:      .p2align 2
2:      .long   0         /* note data: the ABI tag */
         .long   2,4,20    /* Minimum kernel version w/TLS */
3:      .p2align 2        /* pad out section */
#endif /* GLX_USE_TLS */

And once compiled, the library behaved nicely with ldconfig ordering.

The question is, long term is this important to include in the library, 
as 2.4 becomes increasingly scarce. The breaking of a useful toolchain 
function seems more severe than side-effects of loading on an old system...

Is this something I should be asking on the Mesa list?

--Pat