public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andy Arbon <gentoo@andrewarbon.co.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] prelink issues
Date: Mon, 13 Jan 2003 23:06:08 +0000	[thread overview]
Message-ID: <3E234660.3050904@andrewarbon.co.uk> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I've just used prelink on my system and it's thrown up a few errors that
aren't covered in the docs. If someone who understands them could
explain them and any steps that I could take to rectify them I'd really
appreciate it. Some of these appear more than once for different files.

Thanks,

Andy

prelink: /usr/lib/libGLcore.so.1: Library without dependencies

prelink: /usr/bin/gnucash: Could not parse `/usr/bin/gnucash: error
while loading shared libraries: libgal.so.20: cannot open shared object
file: No such file or directory'

prelink: /usr/kde/3.1/bin/artscat: section file offsets not
monotonically increasing

prelink: /usr/lib/transgaming/winex/bin/dosmod: Not enough room to add
.dynamic entry
- -- The docs say that wine(x) won't work.. I'm just curious about what
the error means

prelink: /usr/bin/emacs: COPY relocations don't point into .bss or .sbss
section
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+I0ZeX3TTUvZURBERArcLAJ9j4pO/4PTbpRs3iyuSHLM+pIH9YACgj6LE
ZNKxDj45q2ezlN4uVumhypk=
=beSA
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-01-13 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 23:06 Andy Arbon [this message]
2003-01-14  8:45 ` [gentoo-dev] prelink issues Paul de Vrieze
2003-01-14 12:18 ` Spider
2003-01-14 12:20   ` Andy Arbon
2003-01-14 12:59   ` Mark Gordon
2003-01-14 17:04   ` Evan Powers
2003-01-14 19:13     ` Riyad Kalla
2003-01-14 19:33 ` Dylan Carlson

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=3E234660.3050904@andrewarbon.co.uk \
    --to=gentoo@andrewarbon.co.uk \
    --cc=gentoo-dev@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