configuring buildroot for ARM using Cygwin

[Matt Sartori]

Yet when doing a -v on the uclibc-gcc I got from Keil I get:

Configured with: /home/Unknown/toolchain/build/gcc-3.3.1/configure 
	--target=arm-thumb-elf 
	--host=i686-pc-cygwin 
	--build=i686-pc-cygwin 
	.
	.
	.
	--program-prefix=arm-uclibc-
Thread model: single
gcc version 3.3.1

suggesting that it was built specifically for cygwin, whereas if I do
the same for the one built with buildroot I get:

Target: arm-linux-uclibc
Configured with:
/cygdrive/c/tools/buildroot/toolchain_build_arm/gcc-4.0.2/configure 
	--prefix=/cygdrive/c/tools/buildroot/build_arm/staging_dir 
	--build=i386-pc-linux-gnu 
	--host=i386-pc-linux-gnu 
	--target=arm-linux-uclibc 
	.
	.
	.
Thread model: single
gcc version 4.0.2

Which looks like different options.
What other options do I have if I wanted to build a newer version of
uclibc-gcc that can run under windows/Cygwin?

M@

-----Original Message-----
From: Mike Frysinger [mailto:vapier at gentoo.org] 
Sent: 15 December 2005 14:44
To: Matt Sartori
Cc: uclibc at uclibc.org
Subject: Re: configuring buildroot for ARM using Cygwin

On Thu, Dec 15, 2005 at 11:57:28AM -0000, Matt Sartori wrote:
> When I run make menuconfig (which doesn't seem to display properly in
a
> cygwin window) there seems to be no option to select Cygwin or to tell
> the configuration tool that I'm not on linux. 

the entire point of cygwin is that tools shouldnt care ... cygwin
smells like linux so packages should work just fine

> Unless I explicitly deselect threading support the subsequent make
fails
> when it can't find pthreadtypes.h. Even without it the make fails when
> it can't find elf.h.

last i heard on the crossgcc list, cygwin support sucks because of a
lot of quirks in the filesystem behavior
-mike

--------------------------------------------------------------------------------


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.

If you received this in error, please contact the sender or postmaster (postmaster at hanoverdisplays.com) and delete the material from any computer.

Although we routinely screen for viruses, addressees should check this e-mail and any attachment for viruses. We make no warranty as to absence of viruses in this e-mail or any attachments.

Our Company's email policy is to permit incidental personal use. If this email is of a personal nature, it must not be relied upon as expressing the views or opinions of the company.

Visit out website at www.hanoverdisplays.com