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 Message-ID: <42B58998.9ABB5D44@dessent.net> Date: Sun, 19 Jun 2005 08:04:56 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Compiling memtest from sources on cygwin References: <42B5789F DOT 70201 AT hones DOT org DOT uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com "alexeik AT nordlines DOT ru" wrote: > And since cygwin works under Windows I suspect, that cygwin people setup > the 'as' program to support windows loader. Now I am thinking -- should > I go to linux, or stay with cygwin. Actually I need to write a small > program, which works on bare metall w/o any o/s. You could probably get what you want by building a cross-binutils. Get the binutils source and build with "./configure --host=i686-pc-cygwin --target=i686-pc-linux". Then build memtest with "./configure --target=i686-pc-linux" which should cause it to use the 'i686-pc-linux-as' you just built instead of Cygwin's 'as' which doesn't grok ELF. If memtest has more than just assembly files (i.e. C code too) you'd probably need to build a cross-gcc as well. The whole crosscompiler business is better covered elsewhere, as it's not Cygwin-specific. 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/