X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4F95F18A.6010909@etr-usa.com> Date: Mon, 23 Apr 2012 18:19:22 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Cygwin-L Subject: Re: Why /usr/bin/*.dll must be executable? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. [*] /etc/profile, ~/.bash_profile, ~/.profile, ~/.bash_login... [**] System control panel > Advanced > Environment Variables -- 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