X-Spam-Check-By: sourceware.org Message-ID: <46714555.5CB5CB43@dessent.net> Date: Thu, 14 Jun 2007 06:40:37 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cross compilation References: <5747fc890706140511i7c19f837n7b341293e9d1429c AT mail DOT gmail DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 ICE wrote: > I understand that cygwin does not provide glibc. > does it provide uclibc ??? No. Cygwin itself is a libc. Therefore there is no need for any other, nor would any other even build, since a libc is a very low level system component. > if not how can i create a cross compilation tool chain. Sign. Native and cross are two totally different things. If you've been talking about a cross toolchain this whole time then that changes all the answers. You can't assume we know what you want when you write these terse questions with no details. It is completely possible to build a cross toolchain under Cygwin that includes glibc. See for example the crosstool script and the crossgcc mailing list. But you certainly can't just download glibc and run "./configure", that is a *native* build, and there is no way that will ever work. And just so we're perfectly clear, the resulting output of this cross toolchain would never be executable or usable under Cygwin or under Windows. Brian -- 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/