X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+fJ8rBeuZq2QCOl2M3lsV4 Date: Mon, 11 Jun 2012 10:51:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gcc not running properly?? Message-ID: <20120611145131.GC4004@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <33987996 DOT post AT talk DOT nabble DOT com> <4FD43F56 DOT 6030700 AT gmail DOT com> <498141963 DOT 20120610161732 AT mtu-net DOT ru> <4FD4E7EA DOT 6070101 AT gmail DOT com> <33991064 DOT post AT talk DOT nabble DOT com> <4FD587FF DOT 10207 AT gmail DOT com> <33991319 DOT post AT talk DOT nabble DOT com> <1479297479 DOT 20120611180822 AT mtu-net DOT ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mon, Jun 11, 2012 at 10:45:31AM -0400, Earnie Boyd wrote: >Over at mingw.org we just say that use of the product is not supported >unless you use the shell provided by mingw.org. If you have a >question about why something isn't working and you are using cmd.exe >then try sh.exe first before asking for help. We do not test and >support other scenarios and your use of other scenarios is at your own >support. I see the same being said for cygwin.com but not stated in >such a manner. Running Cygwin commands from the Windows command prompt is certainly supported as long as you aren't trying to use a symlink. It basically boils down to "You have to know what you're doing" which is, I think, What Marco was saying. In general, if you don't really want to understand how this all hangs together it's better to use a shell but that certainly isn't an absolute requirement. If you're comfortable setting the PATH yourself or can figure out where cygwin commands live and understand that some commands are symlinks and will require "ls -l /bin/foo" to figure out a target then there's no reason not to use the command line. -- 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