[Linux-ia64] Bug in dynamic linker (glibc 2.2.2)

[Linux-ia64] Bug in dynamic linker (glibc 2.2.2)

[Francis Galiegue]

Hi,

Well, at least, the dynamic linker says it has a bug, but I don't know whether
it's actually the linker or another component. Bug shows on ia64 but not on
Alpha, x86, Sparc{,64} nor PPC.

The bug: when building qt 2.3.0, using libmng 1.0.0, when it comes to build the
designer, this error occurs when it tries to run uic:

BUG IN DYNAMIC LINKER ld.so: dl-version.c: 217: _dl_check_map_versions:
Assertion `needed != ((void *)0)' failed!

I made a foo test program which only uses mng_version_text() of said library,
tried to link and run it and... it succeeds!

Second thing which I've tried: update my toolchain RPM with RedHat patches,
recompiled libmng with it, then retried qt. Same result.

All calls to ldd uic croak with the same error as well. But calling ldd on foo
succeeds.

I noticed that RedHat fisher uses mng 0.9.4 instead of 1.0.0, and this is what
I will try right now. Has anyone else encountered this bug? What can I do to
chase it down?

-- 
Francis Galiegue, fg@mandrakesoft.com - Normand et fier de l'être
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race"  -- R. Cook

Re: [Linux-ia64] Bug in dynamic linker (glibc 2.2.2)

[Jes Sorensen]

>>>>> "Francis" = Francis Galiegue <fg@mandrakesoft.com> writes:

Francis> The bug: when building qt 2.3.0, using libmng 1.0.0, when it
Francis> comes to build the designer, this error occurs when it tries
Francis> to run uic:

qt is C++, we haven't had nearly as much testing in that are.

Francis> BUG IN DYNAMIC LINKER ld.so: dl-version.c: 217:
Francis> _dl_check_map_versions: Assertion `needed != ((void *)0)'
Francis> failed!

Francis> I made a foo test program which only uses mng_version_text()
Francis> of said library, tried to link and run it and... it succeeds!

When you repor a bug like this you *must* provide a test case. Just
mailing us and saying it doesn't work is no good.

If you can provide a pre-processed file I can take a look at it. There
is no way I am going out compiling Qt on my own. You also need to tell
which toolchain version you are using.

Jes