retracting my retraction [patch included]

[Mohan Embar]

Hi All,

> > Nope, I still need this one too -- or at least something very close to
> > it:
> > 
> >   Index: configure.ac
> >   ===================================================================
> >   --- configure.ac        (revision 120101)
> >   +++ configure.ac        (working copy)
> >   @@ -323,9 +323,9 @@
> >             GCC_UNWIND_INCLUDE=
> >             GCJ="${target_noncanonical}-gcj"
> >          else
> >   -         GCJ="${target_noncanonical}-gcj -B`${PWDCMD-pwd}`/"
> >   +         GCJ="$built_gcc_dir/gcj -B$built_gcc_dir/"
> >          fi
> >   
> > Specifically, without this patch the build process attempts to invoke
> > i386-apple-darwin-gcj (in my case), which does not exist until "make
> > install" happens (and even then, it winds up in the install directory,
> > not accessible to the build).
> > 
> > May I commit this patch?
>
>Yes.

I don't see how this:

> >   +         GCJ="$built_gcc_dir/gcj -B$built_gcc_dir/"

...could possibly be right. Adam, are you building on Linux or Mactel?
What the above line is assuming is that the intermediate compiler is
suitable for building libgcj. This is only true when build=host, which
clearly isn't true for the case when we want to build an i686-pc-mingw32
compiler on i686-pc-linux-gnu using a cross compiler.

If the above is working for you on Mactel, then you're probably
lucking out becuse the intermediate compiler is coincidentally capable of
running on your build machine, even though your build and host strings are
different.

I think the correct assumption is that in order to do crossed-native compiler,
you need to have a cross compiler somewhere in your path, just like
the build-time compiler is assumed to be somewhere in the system path.
That means building the cross compiler, installing it, then adjusting your
system path accordingly before doing the crossed-native build.

-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/