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.


Niibe Yutaka wrote:
> Hi HJ, 
> 
> H . J . Lu wrote:
>  > 2001-04-20  H.J. Lu  (hjl@gnu.org)
>  > 
>  > 	* gcc/configure.in (inhibit_libc): Don't define for Linux.
> [...]
>  > --- gcc-2.96-20000731/gcc/configure.in.cross	Fri Apr 20 10:06:36 2001
>  > +++ gcc-2.96-20000731/gcc/configure.in	Fri Apr 20 10:06:47 2001
>  > @@ -4299,7 +4299,14 @@ fi
>  >  # assert.h.
>  >  inhibit_libc=
>  >  if [test x$host != x$target] && [test x$with_headers = x]; then
>  > -       inhibit_libc=-Dinhibit_libc
>  > +       case "${target}" in
>  > +       *linux*)
>  > +	       # Linux targets have the C library header files.
>  > +	       ;;
>  > +       *)
>  > +               inhibit_libc=-Dinhibit_libc
>  > +	       ;;
>  > +       esac
>  >  else
>  >         if [test x$with_newlib = xyes]; then
>  >                 inhibit_libc=-Dinhibit_libc
> 
> This change is questionable.  There's a situation where we don't have
> C library (yet).  I mean, when we start development of porting, we
> don't have C library.
> 
> Actually, I have such a kind of experience for our GNU/Linux support
> of SuperH.  The bootstrap goes like this.
> 
> 	(1) (Partial) build of GCC (with no C library), install.
>             Language is C only.
> 	(2) Build GNU C library, install.
> 	(3) (Full) build of GCC.  We can support C++ language
> 	    (runtime) or others this time.

This reminds me...

Can we make crt1.asm call __setup_argv_and_call_main or _main depending on
whether or not inhibit_libc is defined?

It's annoying to have the compiler build fail when there is no libc, as
is presently the case.

Toshi


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