This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos 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: trying to build eCos...


Hi, and thanks for you input on the matter...

After fighting with gnude for a while now, I'm starting to realize that
building the toolchain migh be a better option. I've already started looking
at building gcc 3.2.2, because of my previous problem as described. But as
usual new problems appear.

Trying to run the gcc config prior to installing, I get errors becuase it
can't find gcc. The installation manual says that the enviroment variable CC
must point to my native compiler tools. The same thing is stated in the
"building the tools" part of
http://sources.redhat.com/ecos/tools/win-arm-elf.html .

Well, as far as I can figure, I do not have a gcc (native or whatever)
installed ! I read somewhere that it is supposed to come with cygwin, but it
doesn't. I've searched through my whole computer, and no gcc.exe.

So how do I go about building my toolchain then ?

Paul

----- Original Message -----
From: "Bill Knight" <BillK at rosw dot com>
To: "Paul M. Øverby" <paul dot magnar dot overby at spagat dot no>
Sent: Monday, March 03, 2003 2:15 PM
Subject: Re: [ECOS] trying to build eCos...


> Paul
> I have had problems with GNUDE and recently just built the ARM tools
> under Cygwin from scratch.  The work I'm outlining below is not mine.
> I simply collected it and so far it seems to work.
>
> First you will need to get the sources for the following:
> binutils-2.13.2
> gcc-3.2.2
> newlib-1.11.0
> insight-5.3
> I believe all can be found at ftp://sources.redhat.com
>
> I used a slightly earlier version of the build-arm.sh script file
> (attached) to build and install the tools.  The changes to the file
> were to add the --exec-prefix=XXX to the various config lines.
>
> I also found and tracked down a problem in the Insight (gdb) sources.
> I believe there is a patch pending to the tclWin32DLL.c file.  Anyway,
> once I made the single line change as in the attached file, Insight
> compiled and installed OK.  The file is in the insight-5.3\tcl\win
> directory.
>
> The build process does take quite a while.  And unfortunately, if
> things don't work out for you, I may not be of much help.
>
> Good luck.
> -Bill Knight
> R O SoftWare
>
> PS - a couple of things.  Macraigor has a gdb remote program on their
> web site called ARM7LibRemote.  It is very usefull for debugging using
> their Wiggler or Raven JTAG interfaces.  But gdb/Insight is VERY slow
> at downloading via these interfaces.  What I have done is use
> Macraigor's free OCD Commander to download the program, then connect
> via gdb and setup the $PC, then contiune debugging from there.  The
> download for my program via gdb/wiggler was 5+ minutes.  Downloading
> with OCD Commander took about 20 seconds.  You will need to work out
> the details for your specific program and hardware.  This is just a
> suggestion that there is a faster method to download than from within
> gdb/Insight.
>
>



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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