I'm working with Keil uVision environment using the gcc 3.3.1 compiler
and now I want to switch to gcc 4.0.2 so I downloaded the gnuarm
toolchain for cygwin from the www.gnuarm.org.
With the Keil environment the gnu toolchain was installed in the
c:\cygnus directory of my PC and the path was set for
c:\cygnus\arm-tools\bin;c:\cygnus\bin
I removed the old path, renamed the cygnus directory before installing
the new toolchain.
The installer for the gcc 4.0.2 toolchain created the
c:\Programs\gnuarm directory, put the cygwin dll's in
c:\Programs\gnuarm\bin directory together to the gcc exe tools, and
finally set the path to that directory.
The problem is that opening a command line window (my PC runs
Windows2000) and typing arm-elf-gcc nothing occur: simply a new
command line prompt is displayed.
For other tools all is ok: for example typing arm-elf-ar I get the
help screen for that command.
I'm a newbie but what I'm doing wrong?
Thank you for your help.
	

Keil gcc does not use the same toolchain as GNUARM, they do use gcc 
but they use uclibc rather than newlib as the c library.

They will call arm-uclibc-gcc rather than arm-elf-gcc
While you are learning i would recommend you stick with the standard 
installation - you will have enough to learn.

Regards
Spen

--- In lpc2000@lpc2..., "c.barbaro" <c.barbaro@...> wrote:
>
> I'm working with Keil uVision environment using the gcc 3.3.1 
compiler
> and now I want to switch to gcc 4.0.2 so I
downloaded the gnuarm
> toolchain for cygwin from the www.gnuarm.org.
> With the Keil environment the gnu toolchain was installed in the
> c:\cygnus directory of my PC and the path was set for
> c:\cygnus\arm-tools\bin;c:\cygnus\bin
> I removed the old path, renamed the cygnus directory before 
installing
> the new toolchain.
> The installer for the gcc 4.0.2 toolchain created the
> c:\Programs\gnuarm directory, put the cygwin dll's in
> c:\Programs\gnuarm\bin directory together to the gcc exe tools, and
> finally set the path to that directory.
> The problem is that opening a command line window (my PC runs
> Windows2000) and typing arm-elf-gcc nothing occur: simply a new
> command line prompt is displayed.
> For other tools all is ok: for example typing arm-elf-ar I get the
> help screen for that command.
> I'm a newbie but what I'm doing wrong?
> Thank you for your help.
>
	

Unfortunatly I'm not just learning, I'm involved in a
"real" project
in my company.
I'm switching to gcc 4.0.2 to avoid the problem that 3.3.1 compiler
creates compiling interrupt handler code.
However I solved my problem: the gnuarm package is missing the
cygintl-3.dll: downloading apart and putting it in the bin directory
makes the gcc works.
(WinXP generated the missing dll error, Win2K no!)
Compiling my code with newlib instead of uclibc should not make a
great difference for my code since I don't use printf, malloc,
floating point, and so on...
Thank you,

Carlo

--- In lpc2000@lpc2..., "ntfreak2000" <ntfreak2@...> wrote:
>
> Keil gcc does not use the same toolchain as GNUARM, they do use gcc 
> but they use uclibc rather than newlib as the c library.
> 
> They will call arm-uclibc-gcc rather than arm-elf-gcc
> While you are learning i would recommend you stick with the standard 
> installation - you will have enough to learn.
> 
> Regards
> Spen
> 
> --- In lpc2000@lpc2..., "c.barbaro" <c.barbaro@> wrote:
> >
> > I'm working with Keil uVision environment using the gcc 3.3.1 
> compiler
> > and now I want to switch to gcc 4.0.2 so I downloaded the gnuarm
> > toolchain for cygwin from the www.gnuarm.org.
> > With the Keil environment the gnu toolchain was installed in the
> > c:\cygnus directory of my PC and the path was set for
> > c:\cygnus\arm-tools\bin;c:\cygnus\bin
> > I removed the old path, renamed the cygnus directory before 
> installing
> > the new toolchain.
> > The installer for the gcc 4.0.2 toolchain created the
> > c:\Programs\gnuarm directory, put the cygwin dll's in
> > c:\Programs\gnuarm\bin directory together to the gcc exe tools, and
> > finally set the path to that directory.
> > The problem is that opening a command line window (my PC runs
> > Windows2000) and typing arm-elf-gcc nothing occur: simply a new
> > command line prompt is displayed.
> > For other tools all is ok: for example typing arm-elf-ar I get the
> > help screen for that command.
> > I'm a newbie but what I'm doing wrong?
> > Thank you for your help.
> >
>
	

c.barbaro wrote:

>Unfortunatly I'm not just learning, I'm
involved in a "real" project
>in my company.
>I'm switching to gcc 4.0.2 to avoid the problem that 3.3.1 compiler
>creates compiling interrupt handler code.
>However I solved my problem: the gnuarm package is missing the
>cygintl-3.dll: downloading apart and putting it in the bin directory
>makes the gcc works.
>(WinXP generated the missing dll error, Win2K no!)
>Compiling my code with newlib instead of uclibc should not make a
>great difference for my code since I don't use printf, malloc,
>floating point, and so on...
>Thank you,
>
>Carlo
>
>  
>
Gee, I wouldn't use Windows for the host of a "real
project".  Not that 
I am an operating system bigot, I'd run MSDOS and Windows for many 
years, my last purchased Windows was WinNt-4.  During the past 6 years 
I've moved away from Windows platforms for doing embedded software (and 
other software) development.  The bottom line has been the lack of tools 
and reliability, notably that when something went wrong it was difficult 
to find out just what it was that broke.  Another issue was the cost, 
every time I turned around I was spending nickels & dimes for software 
to do things that a "real" operating system should have had.  Those 
nickels & dimes kept adding up.

Having said all this, why not check a out a decent linux distro and see 
if that will do what you need?  After all, cygwin is an attempt at 
imitating the very environment that is Linux!  Linux distros have come a 
huge distance in the past few years, I regularly use Mandriva (currently 
Mandriva-2006) and I find it difficult to believe that a Windows user 
would find themselves completely at a loss when sitting at a Mandriva 
distro.

There is the problem of cost, there is no wiggler for Linux, nor is 
there a suitable USB JTAG debugger (maybe USB == cheap JTAG).  But if 
you are doing a "real project", then a good tools mentality would 
completely disqualify a wiggler?  I use an ethernet based JTAG and gdb 
connects to it just fine (Abatron BDI2000).  The BDI2000 is expensive, 
but it does more than just one processor, or processor family.  It is a 
peice of equipment, and an investment, such as a good 300MHz scope, or 
digitial multimeter would be.

Not for nothing, but is it worth the aggravation of doing development on 
a Windows host?  I've found that I can get so much more done with a 
Makefile than a project file.  Editing source files is so much faster to 
do with a simple, but powerful, editor such as vi (vim) as opposed to 
mouse driven editors.  Tools such as perl, grep, sed, xargs, etc. are 
just "in there" when it comes to a Linux environ while you either have

to purchase them or install into a work-alike such as cygwin.

I've supported an older 8bit product for many years using an MSDOS based 
compiler (Archemedes 8051 C compiler / Assembler).  Over the past 5 
years, I've gradually moved that product development over to Linux.  The 
file editing went first, then the compiler (via dosemu), and finally the 
source went into cvs.  Each step of the way I've experience a large 
productivity increase!  I do things with the makefile such as building, 
then running, test software which validates my data structures (binary 
search arrays).

Support for GNU development tools is still largely from un*x people.  
I'm not aware of a large number of people using cygwin to do 
development.  But then, it may be that I happen to be on IRC channels in 
which only un*x people hang out?

I write code for a living, I strongly encourage fellow coders to check 
out Linux!

Respectfully,

TomW
	>--- In lpc2000@lpc2..., "ntfreak2000" <ntfreak2@...> wrote:
>  
>
>>Keil gcc does not use the same toolchain as GNUARM, they do use gcc 
>>but they use uclibc rather than newlib as the c library.
>>
>>They will call arm-uclibc-gcc rather than arm-elf-gcc
>>While you are learning i would recommend you stick with the standard 
>>installation - you will have enough to learn.
>>
>>Regards
>>Spen
>>
>>--- In lpc2000@lpc2..., "c.barbaro" <c.barbaro@> wrote:
>>    
>>
>>>I'm working with Keil uVision environment using the gcc 3.3.1 
>>>      
>>>
>>compiler
>>    
>>
>>>and now I want to switch to gcc 4.0.2 so I downloaded the gnuarm
>>>toolchain for cygwin from the www.gnuarm.org.
>>>With the Keil environment the gnu toolchain was installed in the
>>>c:\cygnus directory of my PC and the path was set for
>>>c:\cygnus\arm-tools\bin;c:\cygnus\bin
>>>I removed the old path, renamed the cygnus directory before 
>>>      
>>>
>>installing
>>    
>>
>>>the new toolchain.
>>>The installer for the gcc 4.0.2 toolchain created the
>>>c:\Programs\gnuarm directory, put the cygwin dll's in
>>>c:\Programs\gnuarm\bin directory together to the gcc exe tools, and
>>>finally set the path to that directory.
>>>The problem is that opening a command line window (my PC runs
>>>Windows2000) and typing arm-elf-gcc nothing occur: simply a new
>>>command line prompt is displayed.
>>>For other tools all is ok: for example typing arm-elf-ar I get the
>>>help screen for that command.
>>>I'm a newbie but what I'm doing wrong?
>>>Thank you for your help.
>>>
>>>      
>>>
>
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>
	-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------