From: Francis Galiegue <fg@mandrakesoft.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Bug in dynamic linker (glibc 2.2.2)
Date: Tue, 27 Mar 2001 13:36:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005357@msgid-missing> (raw)
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
next reply other threads:[~2001-03-27 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 13:36 Francis Galiegue [this message]
2001-03-27 17:08 ` [Linux-ia64] Bug in dynamic linker (glibc 2.2.2) Jes Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590693005357@msgid-missing \
--to=fg@mandrakesoft.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox