Re: An interface patch

[hjl at varesearch dot com (H.J. Lu)]

> 
>   In message <19990811161445.6348D3FC1@varesearch.com>you write:
>   > > The right way to build cross compilers is with the --with-headers and
>   > > --with-libraries option.  That provides you with a location to search for
>   > > libc.
>   > 
>   > 1. It is for Linux only.
> Just because it is for Linux only does not mean we install a bad patch. 
> 
>   > 2. It is very possible that there is no existing C library when I
>   > build the cross compiler and the purpose of the cross compiler is
>   > to compile the C library. It is a chicken and egg problem.
> No, all you have to do is gather your include files and put them somewhere.
> It's not rocket science.

Are you nuts? We are checking the shared C library here. What can the
include files do for me here?

> 
>   > If you don't like it, just don't include this patch in gcc. I will make
>   > it a Linux patch for gcc.
> If you won't fix the patch, then that's what we'll have to do.  Wrong patches
> will not be accepted. 

Fine. Let's just do that. Oh, boy, it looks like we are getting back to
the old days.

> 
> 
>   > Where do I get those values? As I said, those values have not been
>   > determined yet when config.if is called in gcc/configure.in. They are
>   > empty. My suggestion was to move config.if a few lines down in
>   > gcc/configure.in to where those values have been set.
> So, include that change with your patch.  Again, it's not rocket science.

I never said it was hard. You seem to have some problem to understand
what I said or maybe you just simply don't want to understand.

-- 
H.J. Lu (hjl@gnu.org)