------- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-05-02 15:53 ------- > Just curious: where can I get more information about this issue? We were > linking our shared library statically with libgcc_eh.a in the past with no > problems, and many people on different machines successfully used it. Should > there be any problems?
Theoritically there should be exactly one EH machinery linked in the executable, hence the need for one shared libgcc when there are other shared libraries involved. In practice, if only one shared library has its private EH machinery and if others don't, that may still work. See in the manual the section about -shared-libgcc/-static-libgcc. > By the way, all these tricks were found googling reports of other people who > wanted to link statically. We should probably add links to Google in the manual. :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277
