X-Spam-Check-By: sourceware.org Message-ID: <469406F3.B815A210@dessent.net> Date: Tue, 10 Jul 2007 15:23:47 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: dll libraries marked for random execution? References: <4693D827 DOT 5070609 AT tlinx DOT org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Linda Walsh wrote: > I'd like to get rid of the "executable" bit being set on files that > are not really executable. Besides being bad practice, it also > creates problems when looking for completion values in the shell. Seem > to remember some other issues related to dll's being marked as > executable, but don't recall what they were off-hand... I think Dave already answered most of your questions, but in case it's not clear: everything in /usr/lib is unlinked code in static archives (or libtool files which are plain text), and hence there is nothing there that can be executed, and so there should be no need for the execute bit set on anything in that dir. Windows requires that shared libraries (=DLLs) be either in the same directory as the binary (=EXE) or in the PATH. This is why all shared libraries are in /usr/bin on Cygwin, whereas on *nix they are in /usr/lib. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/