1,9c1,3
< # We need to use -fPIC when we are using gcc to compile the routines in
< # crtstuff.c. This is only really needed when we are going to use gcc/g++
< # to produce a shared library, but since we don't know ahead of time when
< # we will be doing that, we just always use -fPIC when compiling the
< # routines in crtstuff.c. Likewise for libgcc2.c. This is less painful
< # than multilibbing everything with PIC and PIC-not variants.
<
< # The pushl in CTOR initialization interferes with frame pointer elimination.
<
---
> # We multilib libgcc for -fPIC, to get real PIC code in it.
> # NOTE: We must use -fPIC on crt{begi,end}.o else we get an RTLD error
> # "cant set protections on segment of length blah at 0x8048000".
11d4
< TARGET_LIBGCC2_CFLAGS = -fPIC
13,15c6,10
< crti.o: $(srcdir)/config/i386/sol2-ci.asm $(GCC_PASSES)
< sed -e '/^!/d' <$(srcdir)/config/i386/sol2-ci.asm >crti.s
< $(GCC_FOR_TARGET) -c -o crti.o crti.s
---
> MULTILIB_OPTIONS = fPIC
> MULTILIB_DIRNAMES = pic
> MUTLILIB_EXCEPTIONS =
> MULTILIB_MATCHES = fPIC=fpic
> MULTILIB_EXTRA_OPTS =
16a12,14
> LIBGCC=stmp-multilib
> INSTALL_LIBGCC=install-multilib
>