This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

Re: documentation for cross compiling.


Alexandre Oliva wrote:
> 
> On Jan  2, 1997, tm <tm@kloo.net> wrote:
> 
> > I don't understand the full implications of this change, since I
> > haven't looked through newlib yet, but as long as it breaks the
> > sh-coff/sh-elf dependency on newlib and enables a full working
> > compiler to be built without newlib installed, I'm all for it.
> 
> This dependency can't really be broken: GCC is the compiler, and the C
> library, expected to supply crt0.o, libc.a and libm.a are supposed to
> be newlib, in the case of sh-elf and sh-coff.  Of course, if you use
> an alternate C library that supplies crt0.o, libc.a and libm.a such
> that they are compatible with those offered by newlib, you can claim
> there's no dependence on newlib.  The real point is the issue of
> compatibility.  Currently, in order to be compatible, crt0.o must
> implement __setup_argv_and_call_main().  If we move this from crt0.o
> to crt1.asm, it will no longer be the case.  But all other
> dependencies on newlib will remain.

Well, it's a step in the right direction, anyway.

It would be nice if we could print a message when the toolchain is
configured, 
e.g.:

./configure --target=sh-elf
Configuring for sh-elf...
This configuration requires newlib. Please ensure it is installed.

...or something to that effect.

Toshi


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