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:10:53 +0100 [thread overview]
Message-ID: <20011207111053.A23974@ilse.asys-h.de> (raw)
In-Reply-To: <20011206193332.6B8581A542@chiba.3jane.net>; from tneidt@mail.fidnet.com on Thu, Dec 06, 2001 at 07:33:15PM +0000
Hello,
On Thu, Dec 06, 2001 at 07:33:15PM +0000, tneidt@mail.fidnet.com wrote:
> > Are there any conventions on where to store include files? Also, when
> > should one not store files in /usr/lib and instead put a file in
> > /etc/env.d that sets LDPATH? The current package I'm working on defaults
> > to /usr/lib and /usr/include. I've looked in both of these directories
> > and it seems like it should be fine. Is this correct?
If you need to include files from other directories, you should use
the "-I<directory>" compiler-Option, otherwise your source seems to
be buggy (only my opinion) ...
> I also have a somewhat related question. Gentoo Linux doesn't seem to set a
> global LD_LIBRARY_PATH environmental variable like most mainstream linux
> distributions (RedHat, Debian, etc.) do.
It is unnecessary. Using LD_LIBRARY_PATH is also dangerous. It is nothing
more than a workaround (except for cases, where a user wants to use his
own libraries, which are not installed at the "official places).
The "clean way" is to include the library-directories in /etc/ld.so.conf
and to use "ldconfig" to update the cache-file (in this case, setting
LD_LIBRARY_PATH should be unnecessary for using the system-libraries).
> I far as I can tell, this is a _good_ thing.
I don't think so.
> (see http://www.visi.com/~barr/ldpath.html).
It looks to me, that the author of this website thinks, that "LD_LIBRARY_PATH"
ist a very bad idea at all ...
> However, some applications look for this variable.
If an application itself (not only the shared library loader) looks for
LD_LIBRARY_PATH, may be this application is *broken* ...
> Is there a way, around this? Specifically, I've been looking into Webmin
> (http://www.webmin.com/webmin/), and trying to work up some gentoo config
> files for it. The top level config file seems to want LD_LIBRARY_PATH.
Than fix this config file or fix the application. *DON'T TRY TO FIX THINGS
THAT ARE NOT BROKEN!* Setting LD_LIBRARY_PATH globally will IMHO do so ...
> At least that is what is in the config files for the other
> distributions.
Not all, what you will find in other distributions is really good ...
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
next prev parent reply other threads:[~2001-12-07 10:11 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
2001-12-07 14:54 ` Tod M. Neidt
2001-12-07 21:31 ` Daniel Robbins
2001-12-07 10:10 ` Juergen Ilse [this message]
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=20011207111053.A23974@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