This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Building for freescale_twr_k60n512 failing under Cygwin
- From: Michael Bergandi <mbergandi at gmail dot com>
- To: John Dallaway <john at dallaway dot org dot uk>
- Cc: eCos Discuss List <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 21 Feb 2012 01:24:41 -0500
- Subject: [ECOS] Re: Building for freescale_twr_k60n512 failing under Cygwin
- Authentication-results: mr.google.com; spf=pass (google.com: domain of mbergandi@gmail.com designates 10.60.21.8 as permitted sender) smtp.mail=mbergandi@gmail.com; dkim=pass header.i=mbergandi@gmail.com
- References: <CAOHvnTO73Lae_2UBpLQE6SMAvB473XFNb0LQWQ=ED9fgu5kjPQ@mail.gmail.com> <4F42B68D.7070309@dallaway.org.uk>
John,
On Mon, Feb 20, 2012 at 4:09 PM, John Dallaway <john@dallaway.org.uk> wrote:
> Hi Mike
>
> Michael Bergandi wrote:
>
>> I am attempting to exercise the eCos port to the Freescale
>> TWR-K60N512. However, I am currently unable to get it to even build
>> under Cygwin. I have followed the same procedure under Ubuntu 10.04
>> LTS and the build succeeds without issue. Unfortunately, for various
>> reasons, I need this to work on a Windows machine under Cygwin.
>>
>> My current setup is:
>> Windows XP Pro SP3 32-bit
>> Latest cygwin (1.7.10) with tcl-tk bin and src v8.5
>> Current arm-eabi toolchain downloaded from an eCos mirror site
>> eCos from CVS (pulled down today: 2/12/2012)
>> ecosconfig binary from eCosCentric (I have also built my own, but same result)
>
> Check that you are able to invoke arm-eabi-gcc directly from a Cygwin
> bash prompt to compile a trivial C file. Missing packages in a Cygwin
> installation can sometimes lead to silent failure of the compiler.
I actually thought of this and double checked that the listed packages at:
http://ecos.sourceware.org/cygwin.html
were in fact installed. I have everything listed there at least in binary form.
I also invoked the following
$ arm-eabi-gcc.exe -c -o hello.o
-I../twrk60n512/ecosbuild/install/include hello.c
The hello.c is from the example directory and the include directory is
from building the ecos tree outside of cygwin.
I get no complaints from gcc and a hello.o is produced.
Any other ideas?
--
Mike
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss