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: Tue, 7 Jun 2005 15:35:25 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cross compiling cygwin... Message-ID: <20050607193525.GA539@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <4297A14B DOT 9070409 AT plausible DOT org> <20050528131501 DOT V53507 AT logout DOT sh DOT cvut DOT cz> <20050528160424 DOT GB12395 AT trixie DOT casa DOT cgf DOT cx> <429ED094 DOT 9080001 AT tlinx DOT org> <429FAA40 DOT 1050707 AT tlinx DOT org> <429FB310 DOT F17D2674 AT dessent DOT net> <42A5F616 DOT 5090200 AT tlinx DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42A5F616.5090200@tlinx.org> User-Agent: Mutt/1.5.8i On Tue, Jun 07, 2005 at 12:31:34PM -0700, Linda W wrote: >A working cross compiler? Perhaps that is part of the >non-straightforward problem. Have to build non-standard compiler and >whatever other tools are that need to be created especially for such an >environment. This is what I was referring to when I said that I always >seemed to be missing one tool or another that are "obvious" to people >who already have them setup. I guess I somehow thought that since both >were x86 based, there might be some switch tools to produce different >obj/executable formats. A bit naive I suppose... > >It'd be nice if this process was also in the FAQ... There are all sorts of sites out there which deal with creating cross compilers. There is no reason to add this to the FAQ. Just typing "how do I build a cross compiler" into google should be more than adequate. cgf -- 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/