Nathan Coulson wrote: > Glibc-2.28.8 Typo? Current is 2-14.
> I came across the problem in a self made SDL application, with the > following stacktrace > > #0 0x00007f307280a0a9 in do_lookup_x () from /lib/ld-linux-x86-64.so.2 > #13 0x00007f307171090c in SDL_Init (flags=48) at ./src/SDL.c:162 > > and in doing some research, looks like I am not the only person who > got bit by this SDL (me) > rpmbuild: https://bugzilla.redhat.com/show_bug.cgi?id=682307 Says that it is fixed in glibc-2.13.90-6 2011-03-12. I would think the change is in 2.14. > gnucash: https://bugzilla.redhat.com/show_bug.cgi?id=682406 DUPLICATE of bug 682307 > alsautils: https://bugzilla.redhat.com/show_bug.cgi?id=682415 DUPLICATE of bug 682307 > warzone2100 (whatever that is): > https://bugzilla.redhat.com/show_bug.cgi?id=682398 DUPLICATE of bug 682307 > from the above, I am guessing it's a problem with dlsym, and probably > impacts anything that may dynamically load functions. What version of glibc are you using? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
