Message-ID: <4F919ECB.3050909@gmail.com>
Date: Sat, 21 Apr 2012 01:37:15 +0800
From: De-Jian Zhao <dejian.zhao@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Why /usr/bin/*.dll must be executable?
References: <20120420162718.GK22155@calimero.vinschen.de> <2BF01EB27B56CC478AD6E5A0A28931F204483626@A1DAL1SWPES19MB.ams.acs-inc.net> <4F919CF3.70204@cygwin.com>
In-Reply-To: <4F919CF3.70204@cygwin.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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 cyg*.dll" and, of course, it
>> totally hosed Cygwin. I recovered by reinstalling from scratch
>> only after realizing that ATTRIB did not have an option to re-
>> establish X--we're talking XP here.  So, as this is a Windows
>> thing, wondering how, through Windows, I could restore execute
>> access to the DLLs.
>
> What's wrong with "chmod +x cyg*.dll"?
>

It doesn't work any more. You cannot restart a new terminal, either. You 
will be trapped here.


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