|
|||||||||||
|
Re: how to provide extra library paths?
From: P Kapat <kap4lin(at)gmail.com>
Date: Fri Aug 31 2007 - 12:33:31 EDT
Here is Michael's response and my current reply:
On 8/29/07, Michael Marsh <michael.a.marsh@gmail.com> wrote:
Yes I should, thanks. Its just the bad habit of using pine and then switching back to gmail's UI :( > On 8/29/07, P Kapat <kap4lin@gmail.com> wrote: No I am not sourcing any other file... I can provide the two files here if necessary.. > There might be a "helpful" system-wide file that's clearing Ok, I did that. The outcome is the following: When I login remotely (thru ssh) or on a VT, I see the variables from both .bashrc and .bash_profile, as expected I suppose. But when I login to KDE locally, and start a konsole or xterm, only the .bashrc variables are printed out. This again I suppose as is expected that any new shell (either in konsole or xterm) is probably a non-login interactive shell. The funny part is though only .bashrc seems to be sourced when I start a konsole (or xterm) I do have the variables from .bash_profile available, except LD_LIBRARY_PATH. > > > Is there a reason that you don't want to set this in .bashrc? Is LD_LIBRARY_PATH the only way to provide extra library paths? -- Regards PK -------------------------------------- http://counter.li.org #402424 -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Fri Aug 31 12:33:53 2007 This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 03:26:17 EDT |
||||||||||
|
|||||||||||