From mboxrd@z Thu Jan 1 00:00:00 1970 From: H.J. Lu To: egcs@cygnus.com Subject: Re: fixing the c++/f77 circular dependency Date: Mon, 25 Aug 1997 18:48:33 -0000 Message-id: In-reply-to: u9pvr26rln.fsf@yorick.cygnus.com X-SW-Source: 1997-08/0430.html > > >>>>> Jim Wilson writes: > > > I'd like to see them in libgcc.a. It should not be hard to put > > something in libgcc.a from cp/Makefile. > > > I am not opposed to having C++ code in libgcc.a if it can be made to > > work. However, having already dealt with a number of problems resulting > > from this, I am skeptical that it can be made to work cleanly. > > That may be. The code currently in libgcc is the freestanding library, > which includes some code called by various language constructs, and > therefore needs to be linked in automatically. I don't want people to have > to pull in libstdc++ to get RTTI support. > > The only other option would seem to be a third library, linked in along > with libgcc. Then the trick is insinuating it into the specs file. > Could someone please tell me why we cannot put a target libgcc.a in cp/Makefile.in? It will resolve that problem. I am willing to write a patch if people think it is a good idea. -- H.J. Lu (hjl@gnu.ai.mit.edu) From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Galibert To: egcs@cygnus.com Subject: Re: fixing the c++/f77 circular dependency Date: Mon, 25 Aug 1997 19:30:13 -0000 Message-ID: In-reply-to: u9pvr26rln.fsf@yorick.cygnus.com X-SW-Source: 1997-08/0431.html Message-ID: <19970825193013.4gl_HCRTpQ_fh1Vp9lUPWb49qlI0VHoJIxU31IctNL8@z> On Mon, Aug 25, 1997 at 11:32:36AM -0700, Jason Merrill wrote: > The only other option would seem to be a third library, linked in along > with libgcc. Then the trick is insinuating it into the specs file. This would be quite a pain if you want to link together C++ and fortran object files... OG.