From: Caleb Shay <caleb@webninja.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: 04 Jan 2003 20:09:30 -0500 [thread overview]
Message-ID: <1041728970.29666.5.camel@Chinstrap.homeunix.net> (raw)
In-Reply-To: <200301022027.08364.zhen@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
2 things.
1) You spelled "summary" wrong (summery)
2) prelink -famv segfaults for me:
<snip lots of stuff working correctly>
/usr/lib/libnautilus-adapter.so.2 415ec000-415ee494
/usr/lib/libpcreposix.so.0 41152000-41154770
/usr/lib/libcpuaccel.so.0 41288000-41289900
Segmentation fault
Thinking that maybe it was failing on /usr/lib/libcpuaccel.so.0 I tried
prelink -mfv /usr/lib/libcpuaccel.so.0
and that completes without error, so I guess it is segfaulting on
whatever it is trying to prelink next, but I don't know what that is.
Any tips?
Caleb Shay
caleb@webninja.com
On Thu, 2003-01-02 at 20:27, John P. Davis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Thanks to the hard work of Cretin, we now have a guide that explains the ins
> and outs of prelinking in Gentoo. The document can be found here:
> http://www.gentoo.org/doc/en/prelink-howto.xml
>
> Cheers, and have fun!
>
> //zhen
> - --
> John P. Davis
> Gentoo Linux Documentation Developer / Bugzilla Administrator
> http://www.gentoo.org
> #gentoo-doc on irc.freenode.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+FObsYfES/KZpj3kRAhcfAJ9LZK/zL7xHtdRxd42EyaJPqEpmkgCfYsCP
> 9bd8+bMPz971LWxcdY2wN/8=
> =T172
> -----END PGP SIGNATURE-----
>
>
> --
> gentoo-dev@gentoo.org mailing list
--
Caleb Shay <caleb@webninja.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-05 1:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 1:27 [gentoo-dev] Announcing new Prelinking Guide John P. Davis
2003-01-03 8:06 ` Terje Kvernes
2003-01-03 8:25 ` Terje Kvernes
2003-01-03 9:22 ` Stefan Jones
2003-01-03 16:52 ` Terje Kvernes
2003-01-03 19:21 ` Terje Kvernes
2003-01-03 20:54 ` Terje Kvernes
2003-01-04 15:55 ` Stefan Jones
2003-01-04 21:36 ` Terje Kvernes
2003-01-04 14:45 ` Stefan Jones
2003-01-04 22:18 ` Terje Kvernes
2003-01-04 23:11 ` Bart Verwilst
2003-01-04 23:24 ` William Kenworthy
2003-01-05 16:19 ` Paul de Vrieze
2003-01-05 0:10 ` Terje Kvernes
2003-01-03 13:57 ` John P. Davis
2003-01-03 17:23 ` Terje Kvernes
2003-01-03 18:47 ` Toby Dickenson
2003-01-03 19:05 ` Terje Kvernes
2003-01-03 16:11 ` Paul de Vrieze
2003-01-05 1:09 ` Caleb Shay [this message]
2003-01-05 3:12 ` Terje Kvernes
2003-01-05 3:52 ` Caleb Shay
2003-01-05 4:39 ` Caleb Shay
2003-01-05 5:27 ` Terje Kvernes
2003-01-05 6:23 ` Caleb Shay
2003-01-05 7:13 ` Terje Kvernes
2003-01-05 8:01 ` Caleb Shay
2003-01-05 13:20 ` Stefan Jones
2003-01-05 14:30 ` Werner Van Belle
2003-01-05 14:41 ` Stefan Jones
2003-01-05 15:10 ` Dewet Diener
2003-01-05 15:17 ` Bart Lauwers
2003-01-05 15:29 ` Stefan Jones
2003-01-05 14:36 ` Dewet Diener
2003-01-05 5:25 ` Terje Kvernes
2003-01-07 4:02 ` Spider
2003-01-07 7:01 ` Viktor Lakics
2003-01-08 18:49 ` Stefan Jones
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=1041728970.29666.5.camel@Chinstrap.homeunix.net \
--to=caleb@webninja.com \
--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