Can't build gcc for embedded ARC cpu

[Angel Manchado]

On Fri, May 25, 2001 at 09:35:10AM +0300, Kai Ruottu wrote:

> got this error, then what on earth is the problem when you have got GCC
> built (the stuff in 'gcc') ?

I've just been pointed out that I had missed the --with-headers option pointing to newlib's libc/include directory. That's the problem.
I finally built gcc!:) Hurrah!

>  This is also hard to understand... You defined '--with-newlib', which
> means that you know what newlib is and that you are going to use newlib
> as the selected C-library.

I' afraid that I was rather misled regarding newlib's role in the compiler.
I'm so sorry for the confusion.

>  The ARC-support in newlib however is really 'minimal', nothing like
> 'newlib/libc/machine/arc', 'newlib/libc/sys/arc' or 'libgloss/arc'
> in newlib-1.9.0...

Hey! I've tried to build newlib-1.9.0 after gcc's success. It crashed when it tried to 'cd newlib/libc/sys/arc' because it doesn't exist indeed. So what's happening?
(I've just posted this question to the person that helped me, but well you mentioned and I take this opportunity to ask again)

>  If newlib doesn't support the target, the ARC-port serves as an very
> good template, mimicking the definitions for 'arc' in
> 'newlib/configure.host'
> adds just same kind of 'minimal' support, no CPU-specific things, no
> system-specific things, only the 'pure' standard functions compiled for
> the target.

I'm afraid that I don't understand what you mean with this. However, I've taken a look at 'newlib/configure.host' and it turns out that it has these lines:

218    arc-*-*)
219          sys_dir=arc

in a section with the following comment:

"sys_dir should supply system dependent routines including crt0."

Does it mean that I have to get a suitable 'crt0' and place it in 'newlib/libc/machine/arc' ?

Cheers

Angel Manchado


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com