Re: PATCH: Fix native warning

["H. J. Lu" <hjl at lucon dot org>]

On Wed, Dec 18, 2002 at 03:58:05PM -0500, DJ Delorie wrote:
> 
> > That is exactly my concern with adding the "build-" prefix to
> > BUILD_SUBDIR.
> 
> The argument is that if we need a libiberty for both build and target,
> we always want to build the target libiberty with the just-built gcc,
> and never with the bundled compiler.  The one time that happens is
> when build==target yet build != host.

Say build is i686-linux, target is i686-linux and host is ia64-linux.
The just built gcc will be hosted on ia64-linux and targeted for
i686-linux. How do you run the just built ia64-linux gcc binary on
i686-linux? In that case, the compiler used to build gcc is a cross
compiler from i686-linux to ia64-linux. The compiler for build is the
native compiler for i686-linux. When I did that last time, I made sure
the native compiler came from the same source.

> 
> > What if I want to use the current binutils with gcc 3.2?
> 
> I don't see what that has to do with anything.

gcc 3.2 may not have the changes needed for your scheme to work.


H.J.