Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 6 Nov 2002 20:07:28 -0800 (PST) From: Michael A Chase Subject: Re: gcc (as.exe) install error To: cygwin AT cygwin DOT com, Randall R Schulz Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE references: <20021106171425 DOT C31107 AT newwww DOT internal DOT teleologic DOT net><20021106171425 DOT C31107 AT newwww DOT internal DOT teleologic DOT net><5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021106160535 DOT 02086b80 AT pop3 DOT cris DOT com> in-reply-to: <5.1.0.14.2.20021106160535.02086b80@pop3.cris.com> Reply-To: Michael A Chase On Wed, 06 Nov 2002 16:11:49 -0800 Randall R Schulz wrote: > How is the (merely) potential conflict between the output of Danny's > compilation ("test.exe") going to lead "gcc" to produce an "Invalid > argument" error? Especially when the assembler runs (or would run) before > "test.exe" gets written? Also note that "test" is a shell built-in both in > BASH and Ash. True. I focused on the wrong phrases in the problem description. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- 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/