Re: 1.7.7: PATH in Bash shells

[Gerry Reno <greno at verizon dot net>]

On 02/06/2011 07:55 PM, Gerry Reno wrote:
> On 02/06/2011 07:36 PM, Gerry Reno wrote:
>   
>> On 02/06/2011 07:33 PM, Gerry Reno wrote:
>>   
>>     
>>> On 02/06/2011 06:23 PM, David Sastre wrote:
>>>   
>>>     
>>>       
>>>> On Sun, Feb 06, 2011 at 03:43:42PM -0500, Gerry Reno wrote:
>>>>   
>>>>     
>>>>       
>>>>         
>>>>> On 02/06/2011 02:16 PM, David Sastre wrote:
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>>>> On Sun, Feb 06, 2011 at 01:33:37PM -0500, Gerry Reno wrote:
>>>>>>   
>>>>>>       
>>>>>>         
>>>>>>           
>>>>>>             
>>>>>>> What is the proper method to set the PATH variable on a system-wide
>>>>>>> basis in Cygwin?
>>>>>>>     
>>>>>>>         
>>>>>>>           
>>>>>>>             
>>>>>>>               
>>>>>> First off, I'm curious about how do you start the bash shell. I ask
>>>>>> because you don't seem to have PS1 set correctly, and that should be
>>>>>> automated by startup-scripts. 
>>>>>>       
>>>>>>         
>>>>>>           
>>>>>>             
>>>>> I didn't change anything.  This is rather new installation of Cygwin.
>>>>>
>>>>> I have seen some postinstall script failures on a few packages but would
>>>>> these be modifying the system-wide PATH variable?
>>>>>
>>>>> I have not changed anything about PATH anywhere.
>>>>>
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>>>> The PATH variable in cygwin is exported from your /etc/profile
>>>>>> file, which contains a line that sets cygwin's path with higher
>>>>>> precedence over the PATH inherited from windows.
>>>>>>       
>>>>>>         
>>>>>>           
>>>>>>             
>>>>> Yep, I see it.  So why isn't it working?
>>>>>
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>>>>> Is there some guiding document about setting PATH system-wide to better
>>>>>>> support scripts from Linux?
>>>>>>>         
>>>>>>>           
>>>>>>>             
>>>>>>>               
>>>>>>  
>>>>>> Yes. The info you need is in the bash manpage, INVOCATION section.
>>>>>>       
>>>>>>         
>>>>>>           
>>>>>>             
>>>>> bash-4.1$ man bash
>>>>> (END)
>>>>>
>>>>> No man pages.
>>>>> How do you get the man page generated?
>>>>> And here's the tail end of /var/log/setup.log.full:
>>>>>
>>>>>     2011/02/06 12:01:40 running: C:\cygwin\bin\bash.exe --norc
>>>>>     --noprofile /etc/post
>>>>>     install/coreutils.sh
>>>>>     2011/02/06 12:01:41 abnormal exit: exit code=128
>>>>>     2011/02/06 12:01:41 running: C:\cygwin\bin\bash.exe --norc
>>>>>     --noprofile /etc/post
>>>>>     install/bash.sh
>>>>>     2011/02/06 12:01:41 abnormal exit: exit code=128
>>>>>     2011/02/06 12:01:41 running: C:\cygwin\bin\bash.exe --norc
>>>>>     --noprofile /etc/post
>>>>>     install/update-info-dir.sh
>>>>>     2011/02/06 12:02:24 running: C:\cygwin\bin\bash.exe --norc
>>>>>     --noprofile /etc/post
>>>>>     install/libglade2.0.sh
>>>>>     could not open /etc/xml/catalog for saving
>>>>>     add command failed
>>>>>     2011/02/06 12:02:25 abnormal exit: exit code=2
>>>>>     2011/02/06 12:02:25 Changing gid to Administrators
>>>>>     2011/02/06 12:03:00 note: Installation Complete
>>>>>     2011/02/06 12:03:00 Ending cygwin install
>>>>>
>>>>> Problem reports:       http://cygwin.com/problems.html
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>> Well. At this point I'd need you to follow the indications from the
>>>> link above, and attach the ouput from:
>>>>
>>>> cygcheck -s -v -r > cygcheck.out 
>>>>
>>>> to your next post.
>>>> Some extra info I'd need to know: 
>>>> How do you start the shell? As I said, a normal startup should read
>>>> /etc/profile ans set/export your PATH correctly.
>>>> By "normal" startup, I mean a way of calling the shell that tells it
>>>> you are login into cygwin, and therefore, the startup scripts are
>>>> called, e.g. starting mintty (which in turn executes bash --login) is such a way.
>>>> Also, having postinstallation errors from bash and coreutils isn't
>>>> a good thing. I'd try reinstalling both.
>>>>
>>>>   
>>>>     
>>>>       
>>>>         
>>> In response to both David and Csaba:
>>>
>>> Yes, there are both .bash_profile and .bashrc and both of them are same
>>> as the defaults.
>>>
>>> I'm attaching the cygcheck.out file.
>>>
>>> Today when I installed postgresql I noticed that bash got upgraded to
>>> 4.1 and that there were some package postinstall failures like coreutils
>>> and bash.
>>>
>>>
>>> Regards,
>>> Gerry
>>>
>>>   
>>>
>>>     
>>>       
>> You'll notice that I corrected the PATH as shown in cygcheck.out.
>>
>> I did this by editing /etc/bash.bashrc and setting the PATH variable.
>>
>>
>>   
>>     
> BTW,  I start the Cygwin Bash shell from the desktop icon.
>
> Regards,
> Gerry
>
>
>
>
>   
I tried reinstalling Bash and coreutils but still I get postinstall errors:

    Package: coreutils
        coreutils.sh exit code 128
    Package: bash
        bash.sh exit code 128
    Package: Unknown package
        libglade2.0.sh exit code 2


Regards,
Gerry





--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple