Re: [PATCH] Build libgcj, libgcj-tools, and libffi as shared libraries on Windows

["Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>]

Dave Korn wrote:
> Aaron W. LaFramboise wrote:
> > Dave Korn wrote:
>
> > > -  What does this have to do with the top-level LDFLAGS?  I didn't
> > > change them
> > > because I don't want cc1 and cc1plus to also have 128meg of stack, do I?
> > Look at config/mh-mingw, where this is set in LDFLAGS for the entire
> > build.  A while back, someone or other decided that this was the right
> > thing to do.  This value should be propagated into gcc/java, the same
> > way that it is for everything else, but for some weird reason, it
> > doesn't propagate through the build machinery.  The value that is there
> > is large enough for jc1.exe to compile libjava.
> >
> > I think the right thing to do is fix that bug, rather than just hacking
> > it to use the flag that it should already be using, if you see what I mean.
>
>   I notice that those flags get applied to everything in stage1 (xgcc, cc1,
> gen* et al) and not to stages 2 or 3.  Are you sure that isn't intendtional?

OK, I didn't know that.  If that's true, then probably those flags are 
only for the host's compiler.

See <http://gcc.gnu.org/ml/gcc-patches/2008-06/msg00420.html>.  At the 
very least, it was my understanding that the LDFLAGS in mh-mingw were 
*supposed* to fix this.  Apparently, it only worked for non-bootstrap 
cross-builds.

Joseph, what do you think about this?