This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Why /usr/bin/*.dll must be executable?


On 4/23/2012 8:19 PM, Warren Young wrote:
On 4/23/2012 6:12 PM, Richard Troy wrote:

what on earth would --login have to do with where the dlls are found?

Without that, you don't run the profile files[*], so you get the Windows PATH[**] which is clearly insufficient in your situation.

Somewhere in one of these files is a line of code that adds the directory
containing the problem DLL to your PATH.

And the path needed to find DLLs that are provided by the distribution is added in '/etc/profile'. The template for this file can be found in '/etc/defaults/etc'. This file is sourced by default for a login shell.

I can't explain why you might see a difference on W7 with this though,
unless your non-W7 machines added Cygwin paths in the Windows environment
(via cygwin.bat, the control panel that Warren pointed out, or other
scripting files that are part of the your process Richard).

--
Larry

_____________________________________________________________________

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]