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

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

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 c

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

On Mon, 23 Apr 2012, Larry Hall (Cygwin) wrote: > > On 4/23/2012 3:01 PM, Warren Young wrote: > > Options 2-5 in the list at the page linked above don't really apply here. > > Cygwin purposely keeps itself nice and segregated from the rest of the > > system, so installing DLLs under c:\Windows isn

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

On 4/23/2012 2:15 PM, Larry Hall (Cygwin) wrote: On 4/23/2012 3:01 PM, Warren Young wrote: Options 2-5 in the list at the page linked above don't really apply here. Cygwin purposely keeps itself nice and segregated from the rest of the system, so installing DLLs under c:\Windows isn't an option,

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

On 4/23/2012 3:01 PM, Warren Young wrote: Options 2-5 in the list at the page linked above don't really apply here. Cygwin purposely keeps itself nice and segregated from the rest of the system, so installing DLLs under c:\Windows isn't an option, and CWD is simply useless for our purpose here.

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

On Mon, Apr 23, 2012 at 01:02:39PM -0600, Warren Young wrote: > On 4/20/2012 1:06 PM, Jon TURNEY wrote: > > > >'export EXECIGNORE=*.dll' is a cygwin extension to bash to tell it you don't > >want to see those pesky dlls. > > Is there a good reason this isn't in the stock /etc/bash.bashrc? Not tha

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

On 4/20/2012 1:06 PM, Jon TURNEY wrote: 'export EXECIGNORE=*.dll' is a cygwin extension to bash to tell it you don't want to see those pesky dlls. Is there a good reason this isn't in the stock /etc/bash.bashrc? -- Problem reports: http://cygwin.com/problems.html FAQ:

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

On 4/20/2012 7:07 AM, Václav Zeman wrote: This is a Windows thing. Another aspect of the Windows Thing which I have not seen discussed yet is the DLL load path: http://goo.gl/VA8yC Since Windows looks for DLLs first in the *.exe directory, this is the most reliable place to put them. Opti

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

On 4/20/2012 6:10 PM, Mike Kaganski wrote: Any code that may be executed (directly or indirectly) must have "x" under *nix. Windows had tried to make somewhat similar (with the same security concerns in mind) in its NT family, but it had to deal with file systems that have no notion of "executa

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

On 2012-4-21 3:06, Jon TURNEY wrote: On 20/04/2012 14:02, De-Jian Zhao wrote: When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to find the rea

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

On 4/21/2012 5:21 AM, De-Jian Zhao wrote: ... Then, what limitations does the Windows loader have? As far as I know, there is no x bits for windows, right? How does the "chmod a-x" affect the file behavior under Windows if this is a Windows thing? I am completely confused. When I ran "chmod a-x

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

On 20/04/2012 14:02, De-Jian Zhao wrote: > When I type "cyg" and Tab, many executables starting with "cyg" are listed > (Display all 262 possibilities? (y or n) y). I find that many of them are > *.dll libraries under /usr/bin/. This is inconvenient to find the real > executable applications (*.exe

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

On 4/20/2012 2:21 PM, De-Jian Zhao wrote: On 2012-4-21 1:57, Larry Hall (Cygwin) wrote: On 4/20/2012 1:47 PM, De-Jian Zhao wrote: On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao w

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

On 2012-4-21 1:57, Larry Hall (Cygwin) wrote: On 4/20/2012 1:47 PM, De-Jian Zhao wrote: On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wro

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

On 4/20/2012 1:47 PM, De-Jian Zhao wrote: Oh and... At least, *.exe does not respect or even is blind to the -x operation of Cygwin, as abovementioned. Cygwin creates its Windows ACLs to support POSIX permisssions. See the Cygwin Users Guide for more:

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

On 4/20/2012 1:47 PM, De-Jian Zhao wrote: On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote

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

On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many exe

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

On 4/20/2012 1:37 PM, De-Jian Zhao wrote: On 2012-4-21 1:29, Larry Hall (Cygwin) wrote: On 4/20/2012 1:25 PM, Nellis, Kenneth wrote: From: Corinna Vinschen Windows requires the x bit for DLLs to be loadable as executable code into the address space of a process. As Václav wrote, it's a Windows

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

On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Displa

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

From: Larry Hall (Cygwin) > What's wrong with "chmod +x cyg*.dll"? As I said, Cygwin was hosed, so I couldn't enter that command. --Ken Nellis

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

On 2012-4-21 1:29, Larry Hall (Cygwin) wrote: On 4/20/2012 1:25 PM, Nellis, Kenneth wrote: From: Corinna Vinschen Windows requires the x bit for DLLs to be loadable as executable code into the address space of a process. As Václav wrote, it's a Windows thing. So, I had to play with "chmod -x

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

On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I fin

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

On 4/20/2012 1:25 PM, Nellis, Kenneth wrote: From: Corinna Vinschen Windows requires the x bit for DLLs to be loadable as executable code into the address space of a process. As Václav wrote, it's a Windows thing. So, I had to play with "chmod -x cyg*.dll" and, of course, it totally hosed Cyg

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

From: Corinna Vinschen > Windows requires the x bit for DLLs to be loadable as executable code > into the address space of a process. As Václav wrote, it's a Windows > thing. So, I had to play with "chmod -x cyg*.dll" and, of course, it totally hosed Cygwin. I recovered by reinstalling from scra

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

On Apr 21 00:17, De-Jian Zhao wrote: > On 2012-4-20 21:07, Václav Zeman wrote: > >On 20 April 2012 15:02, De-Jian Zhao wrote: > >>Hi, > >> > >>When I type "cyg" and Tab, many executables starting with "cyg" are listed > >>(Display all 262 possibilities? (y or n) y). I find that many of them are > >

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

On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to f

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

On 20 April 2012 15:02, De-Jian Zhao wrote: > Hi, > > When I type "cyg" and Tab, many executables starting with "cyg" are listed > (Display all 262 possibilities? (y or n) y). I find that many of them are > *.dll libraries under /usr/bin/. This is inconvenient to find the real > executable applicat

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

On 2012-4-20 21:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to find the real executable applications (*.ex

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

Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to find the real executable applications (*.exe). Since *.dll files are only libraries