public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Evan Powers <powers.161@osu.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] prelink issues
Date: Tue, 14 Jan 2003 12:04:26 -0500	[thread overview]
Message-ID: <200301141204.26072.powers.161@osu.edu> (raw)
In-Reply-To: <20030114131858.68e0dc79.spider@gentoo.org>

On Tuesday 14 January 2003 07:18 am, Spider wrote:
> its a static library. doesnt use ld.so and cant be prelinkd. neither can
> anything that depends on it. Go Nvidia

I've read this several places now. Since I have a NVIDIA gfx card, I'm 
interested in this issue. ;-)

Question. Is it that binaries that depend on NVIDIA's OpenGL lib can't be 
prelinked /at all/?

I've been trying to find technical descriptions of prelinking for a while now, 
without much luck. The links I get from Google have apparently gone stale....

If the above question is true, it's apparently true that you can't "partially 
prelink" a binary. (Say the binary depends on libfoo.so and libbar.so. I mean 
that it's apparently not possible to prelink references to libfoo.so but 
/not/ references to libbar.so.) Anybody know where I can find out why? Or is 
something else entirely going on?

Evan Powers

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-01-14 17:08 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 [this message]
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=200301141204.26072.powers.161@osu.edu \
    --to=powers.161@osu.edu \
    --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