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 Date: Mon, 26 Nov 2001 18:06:26 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gcc not creating .exe Message-ID: <20011126230626.GB11238@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Mon, Nov 26, 2001 at 02:52:03PM -0800, bucky AT phantom DOT keystreams DOT com wrote: >Excellent! Hiding the cygwin1.dll in /usr/local/lib fixed the gcc >problem, and it also fixed my "disappearing stderr" problem. Why are you putting a version of cygwin in /usr/local/lib??? This is clearly wrong. cgf >On Mon, 26 Nov 2001, Mark Paulus wrote: > >> I also had the problem, but it turns out in my case that I had >> an incompatibility issue between a version of cygwin1.dll that I >> built for debugging, and the production version I downloaded. >> Once I deleted my version in /usr/local/bin, everything worked >> fine once again. >> >> On Mon, 26 Nov 2001 14:22:56 -0800, Collin Grady wrote: >> >> > I had the same issue, where using 'gcc -o hello hello.c' produced >> >nothing. No error, no .exe, nada. I finally solved it by completely >> >reinstalling Cygwin (ugh). Hopefully someone can find a simpler way, but a >> >complete reinstall should fix it, if you're willing to do that. (By complete >> >I mean deleting \cygwin and installing ALL of it from scratch) >> > -Collin Grady >> > >> >Real Users never use the Help key. -- 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/