On Mon, 10 Mar 2014, Rainer Orth wrote: > Rainer Orth <r...@cebitec.uni-bielefeld.de> writes: > > > It does use the host compiler for me, too. > > > >> but maybe _that_ is the issue for you? (see also how it uses > >> -static-libgcc, for me it doesn't even depend on libgcc_s) > > > > But as you can see above, libtool, being its usual helpful self, simply > > drops -static-libgcc ;-( If I use -Wc,-static-libgcc, all seems fine. > > The following patch implements this. The override is necessary to avoid > LDFLAGS passed in from the toplevel to replace the Makefile value. > > Bootstraps on i386-pc-solaris2.10 and x86_64-unknown-linux-gnu are now > well beyond stage1. Ok for mainline if they pass?
If we go that route I wonder if we should rely on the toplevel passing -static-libgcc but instead force -static-libgcc for the plugin anyway? (conditional on compiling with GCC, of course) Thanks, Richard. > Thanks > Rainer > > > 2014-03-10 Rainer Orth <r...@cebitec.uni-bielefeld.de> > > * Makefile.am (comma): New variable > (LDFLAGS): Prefix -static-libgcc with -Wc.
