From: Dylan Carlson <absinthe@pobox.com>
To: Andy Arbon <gentoo@andrewarbon.co.uk>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] prelink issues
Date: Tue, 14 Jan 2003 14:33:51 -0500 [thread overview]
Message-ID: <200301141433.51631.absinthe@pobox.com> (raw)
In-Reply-To: <3E234660.3050904@andrewarbon.co.uk>
On Monday 13 January 2003 06:06pm, Andy Arbon wrote:
> 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.
>
Prelinking is not predictable.
I've got two gentoo systems here in front of me... built almost
identically, but I experienced different results with each. After doing a
prelink -afmR, it's an edgy day of experimenting to figure out what broke.
That said, *most* things work. Some things you won't find until you give
real usage (like my printing failures -- thought I had problem with cups
-- and it was ghostscript giving me a runtime error on account of
prelinking).
Other bins that prelinked without error, and gave me runtime problems:
man/groff/troff, kde's moc, fluxbox. I'm forgetting others.
The moral of the story is, people shouldn't expect everything to work just
because prelink doesn't give an error. IMO it was hasty to unmask
prelink, esp on the eve of 1.4's release... If it were me, I'd make that
a post-1.4 feature.
These issues will go away over time... On my systems, prelinking has been
nice for KDE stuff in particular and that's why I continue to use it.
OpenOffice is still slow. Everything else was probably fast enough
without prelinking to where I don't notice a difference now...
Cheers,
Dylan Carlson [absinthe@pobox.com]
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-01-14 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 23:06 [gentoo-dev] prelink issues Andy Arbon
2003-01-14 8:45 ` 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 [this message]
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=200301141433.51631.absinthe@pobox.com \
--to=absinthe@pobox.com \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo@andrewarbon.co.uk \
/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