(mainline and 3.1) PATCH: Enable shared libgcc on *-*-freebsd[3-]*

Loren James Rittle rittle@latour.rsch.comm.mot.com
Fri Mar 29 14:11:00 GMT 2002

In article <200203290819.g2T8J8v28744@latour.rsch.comm.mot.com>, I wrote:

>>> Permission to apply as is?  David, I would like your approval as well
>>> since this is a fundamental port configuration change.

>> "--disable-shared" will keep the GCC build from making both a shared
>> libgcc[_s].so and libstdc++.so, correct?

> I will have study configuration logic and/or bootstrap with
> --disable-shared to check.  I promise that it will work as you
> desire before I commit (and if a change is required to meet your
> request, I will repost it for comments).

(Probably well-known behavior to the crowd, but) I have verified by
studying the configuration logic and the built gcc/Makefile that no
libgcc_s will be built when gcc is configured with the
--disable-shared option even if the t-slibgcc-elf-ver fragment is
added to a port's tmake_file setting (as I proposed to do in my patch
like other ports already did).

Running --disable-shared bootstrap in a 3.1 tree over night showed no

Applied as previously posted in this thread to mainline and 3.1 branch
(yea, I finally did what I should have done months/years ago ;-).

Thank you Richard and David for the review and comments.


More information about the Gcc-patches mailing list