public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Terje Kvernes <terjekv@math.uio.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: 03 Jan 2003 09:06:20 +0100	[thread overview]
Message-ID: <wxxisx6vern.fsf@nommo.uio.no> (raw)
In-Reply-To: <200301022027.08364.zhen@gentoo.org>

"John P. Davis" <zhen@gentoo.org> writes:

> 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

  well, I ran prelink, found out that all daemons had to be restarted,
  and figured I'd undo and look at it later.   bad idea.

  /usr went full, and now prelink segfaults midway through the KDE
  library directory.  I'm mostly just removing whatever it segfaults
  on and hoping it will continue.  my real problem however is this:

[x200 /] # python2.2
python2.2: error while loading shared libraries: unexpected PLT reloc type 0x00

  which sort of hurts when running Gentoo.  I'm fetching a stage3
  tarball on another system and I'll remerge, hm, kdelibs parts of
  gnome and what have you not once I get this working again.

  one might want to note on the webpage that this _might_ hurt.
  badly.  and maybe python should be protected from optimizations like
  this under Gentoo?

-- 
Terje

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-03  8:08 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 [this message]
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
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=wxxisx6vern.fsf@nommo.uio.no \
    --to=terjekv@math.uio.no \
    --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