Hello

After restoring the original dot profile file, I added a short cut in the
taskbar to lauch /opt/csw/bin/firefox, created an icon and now firefox works
fine when launched in this mode, without the dot profile file's path
appended.

Sivasubramanian M


On Fri, Jun 6, 2008 at 6:39 PM, Sivasubramanian Muthusamy <
isolatedn at gmail.com> wrote:

> Hello
>
> posted again for a response from BOSUG.. The original problem is as oulined
> in the provious messages of the same thread
>
> Sivasubramanian M
>
>
> On 6/5/08, Sivasubramanian Muthusamy <isolatedn at gmail.com> wrote:
>>
>> Hello
>>
>> My new profile file looks as follows:
>>
>> *# ident    "@(#)local.profile    1.10    01/06/23 SMI"
>> stty istrip*
>> PATH=/usr/bin:/usr/ucb:/etc:.
>> export PATH
>> PATH=$PATH:/opt/csw/bin
>> export PATH
>> LD_LIBRARY_PATH=$LD_LIBRARY
>> _PATH:/opt/csw/lib
>> export LD_LIBRARY_PATH
>>
>> How should I exactly modify this to make sure that  /opt/csw/bin is
>> correctly appended ?
>>
>> Sivasurbamanian M
>>
>>
>>
>>
>> On 6/4/08, USM Bish <bish at airtelmail.in> wrote:
>>>
>>>
>>> On Wed, 4 Jun 2008 10:44:03 +0530
>>> "ameya agnihotri" <Using programs in our packages
>>>
>>> >
>>> > Did you set the following environment variables?
>>> >
>>> > PATH=$PATH:/opt/csw/bin
>>> > export PATH
>>> > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/csw/lib
>>> > export LD_LIBRARY_PATH
>>> >
>>>
>>>
>>> This  is a  very  good  input. Actually,  I  had  gone by  the
>>> guidelines given  at http://www.blastwave.org/userguide/ which
>>> in the  section "Using  programs in  our packages"  states the
>>> following:
>>>
>>> <snip>
>>>
>>> 1. Unset LD_LIBRARY_PATH
>>>
>>> 2. Most  important of  all, is  to unset  your LD_LIBRARY_PATH
>>> variable. If you  absolutely must have it set  for some reason
>>> (not recommended), then best results should come if you use
>>>
>>>         # THIS IS NOT A GOOD IDEA
>>>         LD_LIBRARY_PATH='/opt/csw/lib/$ISALIST':/other/values/here
>>>         # THIS IS NOT A GOOD IDEA
>>>
>>> 3. Put /opt/csw/bin  first in your path!!  Particularly if you
>>> want to compile your own tools against blastwave packages. ...
>>>
>>> </snip>
>>>
>>> The thing which caused problems  for me was /opt/csw/bin being
>>> the first thing  in path. For perl, the  default binary became
>>> the  one  from blastwave,  so  /usr/bin/perl  which cpan  uses
>>> failed. I have not tinkered  with $LD_LIBRARY_PATH as yet, but
>>> it is worth giving a try irrespective of what the manual says.
>>>
>>> I  amended the  path to  have  /opt/csw/bin at  the end.  That
>>> sorted out  most of the  issues, barring CPAN, which  is still
>>> complaining. I  think I will re-install  perl and reinitialise
>>> CPAN and see.
>>>
>>> Thanks again,
>>>
>>>
>>> Bish
>>>
>>>
>>> _______________________________________________
>>> ug-bosug mailing list
>>> List-Unsubscribe: mailto:ug-bosug-unsubscribe at opensolaris.org
>>> List-Owner: mailto:ug-bosug-owner at opensolaris.org
>>> List-Archives: http://www.opensolaris.org/jive/forum.jspa?forumID=54
>>>
>>
>>
>>
>> --
>> http://www.linkedin.com/in/sivasubramanianmuthusamy
>>
>
>
>
> --
> http://www.linkedin.com/in/sivasubramanianmuthusamy
>



-- 
http://www.linkedin.com/in/sivasubramanianmuthusamy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/ug-bosug/attachments/20080607/150b5862/attachment.html>

Reply via email to