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


> -----Original Message-----
> From: newlib-owner@sourceware.org [mailto:newlib-owner@sourceware.org]
> On Behalf Of Yaakov Selkowitz
> Sent: Tuesday, March 22, 2016 4:48 PM
> To: newlib@sourceware.org
> Subject: Re: Cross compiling Newlib for ARM in Cygwin
> 
> 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.

Yes, you are right.  This configuration (native Windows GCC
together with Cygwin build environment) fails.

I think this is because GCC does not apply cygpath
to all of its arguments (and also not to its error messages).

(At least the CodeSourcery/Mentor version of GCC is documented
to use cygpath  via the environment variable CYGPATH to translate
file names).


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