From: Chris Brennan <xaero@xaerolimit.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: revdep-rebuild keep on detecting a broken link referred to libqt-mt.so.3
Date: Fri, 29 Feb 2008 12:24:15 -0500 [thread overview]
Message-ID: <47C83FBF.3080905@xaerolimit.net> (raw)
In-Reply-To: <pan.2008.02.29.17.19.47@cox.net>
Duncan wrote:
> Chris Brennan <xaero@xaerolimit.net> posted 47C836DD.50808@xaerolimit.net,
> excerpted below, on Fri, 29 Feb 2008 11:46:21 -0500:
>
>> I'm actually having the same issue as this w/ libqt-mt.so ... my problem
>> this, is gimp won't build because of it. below is the output.
>>
>>
>> /usr/qt/3/lib/libqt-mt.so: could not read symbols: File in wrong format
>> collect2: ld returned 1 exit status
>> make[2]: *** [test-poppler-qt] Error 1 make[2]: Leaving directory
>> `/var/tmp/portage/app-text/poppler-bindings-0.6.1/work/poppler-0.6.1/qt'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> `/var/tmp/portage/app-text/poppler-bindings-0.6.1/work/poppler-0.6.1'
>> make: *** [all] Error 2
>
> Hmm... so what about /usr/qt/3/lib/libqt-mt.so ? Here, it's a symlink
> pointing to libqt-mt.so.3, a symlink pointing to libqt-mt.so.3.3, again a
> symlink, pointing at libqt-mt.so.3.3.8, which is the actual shared-object
> library file.
the point was the error msg from the emerge output about wrong format.
> If you have a valid set of symlinks, pick any one of them and see what
> readelf -h says about it. If the class entry (right under magic) is
> anything other than ELF64, then you have a corrupted library and probably
> need to remerge qt (be sure you remerge qt3 not 4, if you have it merged
> as well). If it's ELF64 and appears to be readable, then you have other
> deeper problems.
I have re-emerged qt-3 numerous times, here is the output of readelf
xaero@Leviathan ~ $ readelf -h /usr/qt/3/lib/libqt-mt.so.3.3.8
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: Intel 80386
Version: 0x1
Entry point address: 0x1b2000
Start of program headers: 52 (bytes into file)
Start of section headers: 7262824 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 6
Size of section headers: 40 (bytes)
Number of section headers: 25
Section header string table index: 24
xaero@Leviathan ~ $
>
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-29 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 9:02 [gentoo-amd64] revdep-rebuild keep on detecting a broken link referred to libqt-mt.so.3 manuel
2008-02-28 19:02 ` [gentoo-amd64] " Duncan
2008-02-29 14:43 ` manuel
2008-02-28 20:15 ` [gentoo-amd64] " Beso
2008-02-29 8:05 ` [gentoo-amd64] a different revdep-rebuild problem and solution Steve Herber
2008-02-29 12:34 ` [gentoo-amd64] " Duncan
2008-02-29 16:46 ` [gentoo-amd64] revdep-rebuild keep on detecting a broken link referred to libqt-mt.so.3 Chris Brennan
2008-02-29 17:19 ` [gentoo-amd64] " Duncan
2008-02-29 17:24 ` Chris Brennan [this message]
2008-03-01 1:52 ` Duncan
2008-03-01 4:11 ` Chris Brennan
2008-03-01 9:08 ` Duncan
2008-03-01 10:10 ` Beso
2008-02-29 16:42 ` [gentoo-amd64] " David Fellows
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=47C83FBF.3080905@xaerolimit.net \
--to=xaero@xaerolimit.net \
--cc=gentoo-amd64@lists.gentoo.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