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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: John Williams Subject: Re: Bug in Cygwin bash? Date: Fri, 04 Apr 2003 07:57:04 +1000 Lines: 18 Message-ID: References: <200304030319 DOT TAA28656 AT ca DOT sandia DOT gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en In-Reply-To: <200304030319.TAA28656@ca.sandia.gov> friedman_hill ernest j wrote: > I think John Williams wrote: > >>It seems not many people build linux kernels under cygwin - I think >>if they did, this issue I've found would have been reported earlier, >>because it's the first step in the kernel configuration process. > > > OK, I've gotta ask -- WHY do you want to do this in the first place? Porting uClinux to an embedded target, the toolchain for which runs under Cygwin. I agree it would be somewhat perverse to build an i386 linux kernel under Cygwin! Cheers, John -- 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/