public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dewet Diener <gentoo@dewet.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Announcing new Prelinking Guide
Date: Sun, 5 Jan 2003 17:10:20 +0200	[thread overview]
Message-ID: <200301051710.20547.gentoo@dewet.org> (raw)
In-Reply-To: <1041777696.1422.32.camel@localhost>

Op Sun 05 Jan 03 16:41 skrewe Stefan Jones:
> If you use -f you get around that problem, but you then encounter
> the other one, you are between a rock and a hard place it seems.

After more poking around, I found that I have an older libstdc++ still lying around:

lrwxrwxrwx    1 root     root           18 Dec 17 00:32 libstdc++.so -> libstdc++.so.5.0.2
lrwxrwxrwx    1 root     root           18 Dec 17 00:32 libstdc++.so.5 -> libstdc++.so.5.0.2
-rwxr-xr-x    1 root     root      1077104 Nov 24 05:34 libstdc++.so.5.0.1
-rwxr-xr-x    1 root     root      1083538 Dec 17 00:31 libstdc++.so.5.0.2

5.0.1 prelinked without the segfault, and I got most everything depending on libstdc++ working fine by symlinking it to 5.0.1 instead of 5.0.2.  However, arts (and a whole lot of kde stuff) seems to be unhappy about that...

Dewet

-- 
Dewet Diener   <gentoo@dewet.org>   http://dewet.org
Professional Student, avid Gentoo user :)
Stellenbosch, South Africa (33º 55" 58.80'S  18º 51" 00.00'E)

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-05 15:13 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
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 [this message]
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=200301051710.20547.gentoo@dewet.org \
    --to=gentoo@dewet.org \
    --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