Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <2C08D4EECBDED41184BB00D0B747334202FB4426@exchanger.cacheflow.com> From: "Karr, David" To: "'cygwin AT cygwin DOT com'" Subject: Still trying: linked executable runs in DOS and cygwin.bat, but n ot Bash inside XEmacs, except in "cmd /c" Date: Mon, 4 Jun 2001 10:25:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" I asked about this a while ago, but I have a tiny bit more information. Perhaps this new information will spark someone's neurons. I have an application which our build system builds, and which is an intermediate target which is used to build other things. The intermediate target is an executable which is linked by the "Segmented Executable Linker" (version from 1994), as opposed to the "Incremental Linker" (at least newer than 1998, most likely). When I execute this application from DOS, it works fine. When I execute this application from a Bash shell created by "cygwin.bat", it also works fine. However, when I execute this application from a Bash shell from within XEmacs-Cygwin, it fails immediately with "Permission Denied". This happens before it gets to the code of the application. I put a printf at the top of "main", and it didn't get there. If I execute "cmd /c execname" from the XEmacs bash shell, instead of just "execname", it appears to work. I don't want to make our build system wrap the execution with "cmd /c", but I will if I can't find any alternative. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple