This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Cross compiling Newlib for ARM in Cygwin

From: Mike Frysinger <vapier at gentoo dot org>
To: Yaakov Selkowitz <yselkowitz at cygwin dot com>
Cc: newlib at sourceware dot org
Date: Tue, 22 Mar 2016 13:28:50 -0400
Subject: Re: Cross compiling Newlib for ARM in Cygwin
Authentication-results: sourceware.org; auth=none
References: <A45B1767F1002449A37508C2CC6003D72DD106 at DEFTHW99EJ1MSX dot ww902 dot siemens dot net> <56F1691B dot 6050403 at cygwin dot com>

On 22 Mar 2016 10:47, Yaakov Selkowitz wrote:
> On 2016-03-22 09:33, Schwarz, Konrad wrote:
> > pardon my obtuseness: I'd like to build newlib for the arm-none-eabi target on a Cygwin host.
> >
> > I have a arm-none-eabi GCC and Binutils which was built for native Windows.
> 
> Cygwin != native Windows.  If you want to use a Cygwin shell for 
> cross-compiling, then you'll want Cygwin-hosted cross-compilers.
> 
> > I have downloaded newlib-cygwin in directory ./newlib-cygwin .  I create a directory ./newlib-cygwin-arm, and
> >
> > $ export CC=arm-none-eabi-gcc
> > $ cd newlib-cygwin-arm
> > $ ../newlib-cygwin/configure
> 
> That is not how cross-compiling works.  Cross-compiler toolchains 
> (binutils/gcc/gdb/newlib) are built by configuring with the desired 
> --target.

i think you mean --host
-mike

Attachment: signature.asc
Description: Digital signature

Follow-Ups:
- Re: Cross compiling Newlib for ARM in Cygwin
  - From: Yaakov Selkowitz

References:
- Cross compiling Newlib for ARM in Cygwin
  - From: Schwarz, Konrad
- Re: Cross compiling Newlib for ARM in Cygwin
  - From: Yaakov Selkowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]