public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Juergen Ilse <juergen@ilse.asys-h.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] standards/conventions? (LDPATH, include files)
Date: Fri, 7 Dec 2001 11:56:17 +0100	[thread overview]
Message-ID: <20011207115617.B23974@ilse.asys-h.de> (raw)
In-Reply-To: <0GNX002LETCX3G@mxout2.netvision.net.il>; from danarmak@gentoo.org on Thu, Dec 06, 2001 at 09:43:16PM +0200

Hello,

On Thu, Dec 06, 2001 at 09:43:16PM +0200, Dan Armak wrote:
> In Gentoo LD_LIBRARY_PATH is called simply LDPATH.

I don't think so. LD_LIBRARY_PATH ist relevant for the shared library loader
ld.so (see also "man ld.so"). LDPATH is (as far as i know) not relevant for
ld.so. LDPATH and LD_LIBRARY_PATH are IMHO totally different things (and
IMHO should LD_LIBRARY_PATH not be set to a default value).

> Legend has it drobbins simply renamed it because he was tired of typing
> the longer version :-)

Is it some kind of "urban legend"? ;-)
I also did a "strings /lib/ld.so | grep LD" to see, if ld.so was modified
to accept LDPATH instead of "LD_LIBRARY_PATH" and i saw no "LDPATH" in,
so the meaning of LD_LIBRARY_PATH seems not to be modified and LDPATH seems
not to "replace" LD_LIBRARY_PATH ...

> Under /etc/env.d you will see a lot of files setting that variable.
 
... which is not the same as LD_LIBRARY_PATH ...

> However, it doesn't actually get exported to your shell. Instead, env-update 
> changes /etc/ld.so.conf to include those dirs.
 
IMHO is that "the right thing" to do.

> So if you app is well written just let it think LD_LIBRARY_PATH is empty and 
> that everything is ni standard dirs - it is. Is that approach problematic?
 
No.

ciao,
	Juergen Ilse					(ilse@asys-h.de)
-- 
Wenn ich auch nur aus jedem 1000. Bug in einem M$ Produkt|Juergen Ilse
einen Tag trauern wollte, also da muesste ich 300 Jahre  |Internet POP Hannover
alt werden und wuerde mehrere Dutzend schwarze Anzuege   |Vahrenwalder Str. 205
aufbrauchen. (Detlef Bosau in dcoulm)                    |30165 Hannover


  parent reply	other threads:[~2001-12-07 10:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 19:33 [gentoo-dev] standards/conventions? (LDPATH, include files) tneidt
2001-12-06 19:43 ` Dan Armak
2001-12-06 20:47   ` Zach Forrest
2001-12-06 20:53     ` Dan Armak
2001-12-06 22:05       ` Zach Forrest
2001-12-07 10:56   ` Juergen Ilse [this message]
2001-12-07 14:54     ` Tod M. Neidt
2001-12-07 21:31     ` Daniel Robbins
2001-12-07 10:10 ` Juergen Ilse
2001-12-07 14:33   ` Tod M. Neidt
2001-12-07 21:33     ` Daniel Robbins
  -- strict thread matches above, loose matches on Subject: below --
2001-12-06 18:51 Zach Forrest

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=20011207115617.B23974@ilse.asys-h.de \
    --to=juergen@ilse.asys-h.de \
    --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