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: Sun, 21 Sep 2003 11:51:24 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: CC1 Message-ID: <20030921155124.GD21177@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Sep 21, 2003 at 12:34:24AM -0500, Robert McNulty Junior wrote: >I had a problem solved by going into /etc/profile > >cc1 was needed by 3.3.1 gcc. The directory where cc1 resides >(/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1 needed to be placed in the path, so I >added that to my profile under path. No, no it does not need to be in the path with this or any other gcc. >HTH someone facing similar problems in the future. Please disregard this advice. If you have this problem, there is something else going on. I suspect it is as simple as the fact that I forgot to take gcc-mingw out of test. Upgrading to gcc-mingw-20030911-2 should solve any problems with gcc -mno-cygwin . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/