Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Mon, 17 Jun 2002 14:45:04 -0400 From: Jon LaBadie To: cygwin@cygwin.com Subject: PATH setting in compiled apps Message-ID: <20020617184504.GA20595@butch.jgcomp.com> Mail-Followup-To: Jon LaBadie , cygwin@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i I'm compiling an amanda backup application. The executables are going into a directory /usr/local/lib/amanda. I've not determined where it is occuring, but it appears the apps are setting PATH with their own directory prepended to the PATH. However, the PATH to which c:\cygwin\usr\local\lib\amanda is prepended is not my system wide environment PATH. I.e. it does not contain c:\cygwin\bin. Just some of the windows system dirs. The result is that when the app is started by inetd, I get a windows popup error about a missing cygwin1.dll. If I copy the dll to the amanda executable directory (in the PATH reported in the popup) it runs fine. Two cygwin1.dll's are certainly not desireable. And symlinks to the single dll did not work. I will continue to check the amanda source for a problem. However, in case there is something about compiliing cygwin apps I'm missing, or in the way cygwin's inetd works I'm missing, I'll ask if anyone has an idea? -- Jon H. LaBadie jcyg@jgcomp.com JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/